Tagged articles
Saga pattern
15 articles · Page 1 of 1
This article systematically categorizes and explains core microservice design patterns across decomposition, integration, database, event-driven, observability, and cross-cutting concerns, providing practical guidance for architects building resilient, scalable distributed systems.
API GatewaySaga patternarchitecture
0 likes · 23 min read

This article presents a comprehensive software design methodology spanning strategic design (bounded contexts, domain partitioning, architectural style selection), tactical design (functional and non-functional modeling), structural modeling (class responsibilities, package structure), behavioral modeling (sequence diagrams, state machines), and DFX (design for performance, reliability, cost) — with concrete code examples and real-world failure patterns.
Bounded ContextCircuit BreakerSaga pattern
0 likes · 34 min read

In an 80-minute interview, Turing Award winner Mike Stonebraker argues that relational databases will absorb AI workloads, explains why Text-to-SQL fails on real enterprise data due to schema corruption and access controls, details DBOS's persistent workflow approach for AI agents, and discusses saga patterns for compensating transactions, graph database limitations, and the future of open-source AI.
AI agentsDBOSGraph Databases
0 likes · 27 min read

This article provides a comprehensive overview of microservices architecture, covering bounded contexts, service granularity, API layers, sidecar/service mesh patterns, communication styles, data topology, distributed transactions with Saga, common anti-patterns, characteristic ratings, and team topology alignment.
Bounded ContextSaga patterndatabase-per-service
0 likes · 23 min read

This article provides a comprehensive guide to integrating Temporal with Spring Boot for handling long-running distributed transactions, covering core architecture, Saga compensation patterns, activity retries, versioning, debugging, transaction boundary isolation, multi-tenancy, and production monitoring with concrete code examples and pitfalls.
Saga patternSpring BootTemporal
0 likes · 21 min read

This article explains core fault‑tolerance principles for distributed systems, covering isolation, redundancy, health checks, failure detection, automatic recovery, consistency trade‑offs, Saga transactions, monitoring, prediction, and team practices to create resilient, maintainable architectures.
KubernetesSaga patternfault tolerance
0 likes · 10 min read

This article explores the challenges of maintaining data consistency in distributed microservice architectures, covering CAP theory, consistency models, replication strategies, transaction patterns like Saga and TCC, tooling choices, monitoring practices, and actionable best‑practice recommendations.
CAP theoremData ConsistencySaga pattern
0 likes · 13 min read

This article explores the challenges of maintaining data consistency in microservice architectures and presents practical solutions such as distributed transactions, Saga patterns, event sourcing with CQRS, message‑queue choices, database strategies, monitoring techniques, and best‑practice guidelines for reliable implementation.
Data ConsistencySaga patterndistributed transactions
0 likes · 11 min read

This article explores the challenges of data consistency in distributed systems, explains fundamental concepts such as CAP and BASE, compares industry solutions like 2PC, Saga, TCC, and local message tables, and shares practical insights from payment service refactoring and Alipay's DTS framework.
BackendCAP theoremData Consistency
0 likes · 23 min read

This article explains the fundamentals of distributed transactions, compares classic solutions such as XA, Saga, TCC, local message tables, and transactional messages, discusses their trade‑offs, and introduces advanced techniques like sub‑transaction barriers to handle network anomalies in microservice architectures.
DTMSaga patternTCC
0 likes · 16 min read

This article explains why each microservice should own its own database, outlines four data‑sharing approaches, describes how to perform backward‑compatible schema changes, and introduces the Saga pattern for cross‑service transactions, providing practical guidance for building robust microservice architectures.
Database DesignSaga patternbackward compatibility
0 likes · 14 min read

The article explains why achieving data consistency across multiple microservices is challenging, reviews the limitations of two‑phase commit, and presents practical techniques such as the Saga pattern, reconciliation, event logs, orchestration vs. choreography, and change‑data‑capture to keep distributed systems eventually consistent.
CDCData ConsistencySaga pattern
0 likes · 12 min read

The article explains the Saga pattern as a solution for managing distributed transactions in microservice architectures, comparing event‑driven choreography and command‑oriented orchestration approaches, and discusses their benefits, drawbacks, and rollback strategies.
Event ChoreographySaga patterncompensation
0 likes · 9 min read

This article explains why transactions are essential, traces their origin from early XA specifications, examines the CAP and BASE theories that expose challenges in distributed systems, and reviews practical solutions such as two‑phase commit, three‑phase commit, TCC, asynchronous messaging, Saga and Gossip protocols, highlighting their trade‑offs and when to apply each.
BASE theoryCAP theoremSaga pattern
0 likes · 17 min read

The article explains the necessity of transactions, traces their origins from database XA specifications to modern distributed systems, compares CAP and BASE theories, and reviews mainstream solutions such as two‑phase commit, three‑phase commit, TCC, asynchronous messaging, and the Saga pattern.
BASE theoryCAP theoremSaga pattern
0 likes · 14 min read
