Sagas — Part 4: Design Considerations Sagas — Part 1: An Introduction Sagas — Part 2: Sagas in Distributed System Sagas — Part 2b: Sagas in Distributed Systems Continued Sagas…
Sagas — Part 2: Sagas in Distributed Systems In the previous post in this series, I briefly touched on why distributed transactions are not suitable in distributed systems:
Re-designing an Aggregation Microservice — Part 2 In the first post in this series, I introduced the current design of the reporting service. And discussed some of the issues with that…
Re-designing an Aggregation Microservice — Part 1 I was involved in a recent discussion regarding how to improve a reporting microservice that aggregates data from numerous services. There…
Re-implementing the Outbox Pattern in MongoDB I have blogged previously about how we implemented the Outbox pattern on top of SQL Server and Websphere MQ to avoid distributed…
Architecture DTC-Enforced Constraints There are numerous blogs and talks out there about why you should or should not use distributed transaction coordinators (DTC) and they…
Avoiding Distributed Transactions — Outbox Pattern I’m currently architecting a payment system for domestic payments for a UK bank. This is a greenfield system that is going to consist of a…
Architecture Scalability and SOA — Part 3 (UI Composition) In part 2, I briefly covered Event-Driven SOA and why event messages are preferred for communication between services. I also stated that…
