Design Considerations
Okay, so that's a look at COM+ transactions. To wrap it up, consider some of the critical design issues involved with COM+ transactional component construction.
Prefer Fine-Grained Components
Don't maintain transactions across method calls. Objects operating at a granularity of one transaction per method call perform much better than coarser-grained components. Requiring several client method calls to complete an operation produces objects that scale poorly because transaction resources (DTC Transaction objects, database connections, COM+ object state, and so on) have to be maintained by COM+ during the interim.
Fine-grained solutions are not only highly scalable but also much easier to debug. If each method call stands ...
Get COM+ Unleashed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.