6.7. Performance Problems of Asynchronous Drawbridges
Now that I have convinced you to use asynchronous drawbridges based on message queues, I will take the opposite viewpoint: I'll tell you why you shouldn't.
The biggest problem with asynchronous drawbridges based on message queues is that they force you to involve our old friend DTC, the distributed transaction coordinator. Remember DTC? She's the one required when a transaction involves more than one transactional resource—say, a database and a message queue. These are the types of transactions we're using when our donor fortress both updates a local database and makes an asynchronous interfortress request from within the same transaction.
There is a huge difference between a tightly coupled ...
Get Software Fortresses: Modeling Enterprise Architectures 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.
