1d ago · 14 min read · TLDR: A Saga replaces fragile distributed 2PC with a sequence of local transactions, each backed by an explicit compensating transaction. Use orchestration when workflow control needs a single brain; use choreography when services must stay loosely c...
Join discussion1d ago · 12 min read · TLDR: Microservices get risky when teams distribute writes without defining how business invariants survive network delays, retries, and partial failures. Patterns like transactional outbox, saga, CQRS, and event sourcing exist to make those rules ex...
Join discussionJan 23 · 24 min read · Introduction In the world of microservices architecture, managing distributed transactions across multiple services is one of the most challenging problems developers face. Traditional ACID transactions that work seamlessly in monolithic applications...
Join discussionJan 14 · 6 min read · Introduction What happens when a trade partially succeeds? Your order is placed, funds are reserved… but settlement fails. Do you roll back? Retry? Compensate? And how do you prove your system behaves correctly when the market, network, or exchange m...
Join discussion
Dec 3, 2025 · 16 min read · The promise of distributed systems - scalability, resilience, and independent deployability - often comes with a steep price: managing data consistency across multiple, autonomous services. As systems decompose from monoliths into microservices, the ...
Join discussionSep 29, 2025 · 21 min read · The journey towards scalable, resilient systems invariably leads us to microservices. We break down monolithic applications into smaller, independently deployable services, each managing its own data store. This architectural shift, while offering im...
Join discussionJul 7, 2025 · 10 min read · What is a Transaction? A transaction is a series of actions that must all be executed successfully. If any one of the actions fails, the entire set of operations is rolled back, leaving the system in its previous stable state. A transaction has the f...
Join discussionJun 7, 2025 · 3 min read · Introduction In distributed systems, maintaining data consistency across multiple services is challenging, especially in financial applications where transactions must be atomic and reliable. The SAGA pattern is a design pattern that helps manage dis...
Join discussionFeb 7, 2025 · 4 min read · The Problem: Partial Failures in Payments Modern payment systems often involve multiple services: Reserve Funds (Bank API) Charge Customer (Payment Gateway) Update Inventory (Inventory Service) Send Confirmation (Email Service) Partial Failure ...
Join discussionFeb 4, 2025 · 1 min read · Lately, I’ve been working on a project with features like e-commerce integration, video conferencing, and event-based scaling. The big question? Monolith or Microservices? The hype around microservices is real. Many advocate for it as the default arc...
Join discussion