Comments on: Something that’s gonna bite us http://www.simonlin.ca/2006/11/07/something-thats-gonna-bite-us/ A site by Simon Lin Tue, 24 Jun 2008 17:59:51 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Jeff Perrin http://www.simonlin.ca/2006/11/07/something-thats-gonna-bite-us/comment-page-1/#comment-10 Jeff Perrin Mon, 13 Nov 2006 17:01:03 +0000 #comment-10 <p>"Note that each facade method has its own transaction. So if one of the task fails, it will just rollback itself, not the whole bundle."</p> <p>I thought about this as well, but just assumed it had been addressed before. Maybe it hasn't been brought up, though?</p> <p>I also wonder if this is one way we could get some good performance gains. If we could come up with a way of injecting one Unit of Work into multiple facade calls we could address the rollback issue, and possibly make things faster by not ditching our object caches after each facade method (transaction).</p> <p>For example, our battery oil process task bundle must make about 10 separate facade calls. Perhaps our workflow stuff should sit just below the facade instead of above it.</p> “Note that each facade method has its own transaction. So if one of the task fails, it will just rollback itself, not the whole bundle.”

I thought about this as well, but just assumed it had been addressed before. Maybe it hasn’t been brought up, though?

I also wonder if this is one way we could get some good performance gains. If we could come up with a way of injecting one Unit of Work into multiple facade calls we could address the rollback issue, and possibly make things faster by not ditching our object caches after each facade method (transaction).

For example, our battery oil process task bundle must make about 10 separate facade calls. Perhaps our workflow stuff should sit just below the facade instead of above it.

]]>