Tagged articles
Outbox Pattern
20 articles · Page 1 of 1
This article details how to build a production-grade order service using Kratos v2, MySQL, Kafka, and Kubernetes, covering idempotency keys, outbox pattern, inventory reservation, state machines, context/timeouts, middleware, observability, Kubernetes probes, capacity planning for 8000 QPS, and automated fault-injection tests.
IdempotencyInventory ReservationKratos
0 likes · 63 min read

This article details production-ready Go distributed transaction patterns including Outbox for reliable event publishing, RocketMQ transaction messages, SAGA orchestration with compensation, TCC resource reservation, payment unknown-state handling, capacity planning, fault validation matrices, and operational recovery loops with concrete PostgreSQL schemas and Go code examples.
GoOutbox PatternPostgreSQL
0 likes · 45 min read

This article details a production-ready messaging architecture using Go and NATS JetStream, covering transactional outbox publishing, consumer idempotency via inbox tables, aggregate version ordering strategies, quarantine and recovery workflows, Kubernetes R3 deployment, capacity planning, and acceptance testing against failure injection scenarios.
Event OrderingGoKubernetes
0 likes · 40 min read

This article presents a production-grade design for handling long-running, preemptible worker tasks in Go and PostgreSQL, covering lease protocols, fencing tokens, outbox patterns, and side-effect reconciliation to prevent stale workers from corrupting state or duplicating external operations.
FencingGoIdempotency
0 likes · 37 min read

The article explains how to handle duplicate payment callbacks in Spring Boot using database unique constraints, conditional state updates, an outbox pattern for reliable event publishing, and downstream idempotency, ensuring orders are processed exactly once even if the payment platform sends repeated notifications.
IdempotencyOutbox PatternSpring Boot
0 likes · 17 min read

This article details the evolution of a product semantic recall system using Spring AI Embedding, covering architecture design, reliable vector indexing with Outbox pattern, hybrid search fusion, pgvector HNSW tuning, and safe migration to Milvus, with production readiness criteria and observability practices.
EmbeddingHybrid SearchMilvus
0 likes · 20 min read

This article explores why cross-service state management is harder than API design in distributed systems, using a refund example to illustrate how local transactions, idempotency, state machines, Outbox patterns, and manual intervention achieve recoverable convergence when operations span multiple services and external channels.
ConsistencyIdempotencyOutbox Pattern
0 likes · 21 min read

The article walks through why embedding a wallet in the order service leads to boundary violations and failures under load, and presents a step‑by‑step evolution from an order‑centric wallet to a dedicated, event‑driven accounting center that ensures consistency, auditability, and high‑throughput scalability.
IdempotencyMicroservicesOutbox Pattern
0 likes · 42 min read

The article explains that a production‑grade wallet must store balance snapshots instead of summing transaction flows, using double‑entry bookkeeping, ACID guarantees, idempotent request handling, outbox messaging, sharding, and comprehensive reconciliation to ensure correctness and high‑throughput under heavy concurrency.
IdempotencyOutbox Patternbalance snapshot
0 likes · 43 min read

This article dissects common MQ mis‑selections, categorises four message types, explains the five architectural roles of a message broker, compares Kafka, RabbitMQ and Pulsar on capabilities and trade‑offs, and provides a step‑by‑step selection guide with real‑world code snippets and best‑practice patterns.
KafkaOutbox PatternPulsar
0 likes · 26 min read

This article dissects why modern systems must enforce three reliability guarantees—no message loss, no duplicate processing, and no out‑of‑order delivery—by examining real‑world order flows, outbox patterns, idempotent keys, partitioning strategies, consumer acknowledgments, and operational safeguards such as replay, dead‑letter handling, and monitoring.
IdempotencyKafkaOutbox Pattern
0 likes · 28 min read

This article details a production-ready cross-database synchronization architecture using CDC and Outbox pattern with Spring Boot, Debezium, and Kafka, covering schema design, connector configuration, transaction boundaries, ordering guarantees, idempotent consumption, dead-letter queues, and monitoring strategies.
CDCCross-Database SyncData Consistency
0 likes · 20 min read

This guide details implementing CQRS and Event Sourcing in Spring Boot, covering command/query separation, event bus choices (Outbox pattern, Kafka), projection idempotency, state snapshots for performance, Saga-based compensation for distributed transactions, and practical tuning tips for production workloads.
CQRSEvent BusIdempotency
0 likes · 14 min read

The article explains why cross‑aggregate business logic belongs in domain services, how domain events capture immutable business facts, and demonstrates practical Spring Boot implementations—including in‑process publishing, message‑queue integration, and the Outbox pattern—while highlighting pitfalls and verification techniques.
Domain EventDomain ServiceOutbox Pattern
0 likes · 10 min read

This article analyses why delayed messaging is a critical system bottleneck, compares RabbitMQ and RocketMQ implementations—including TTL+DLX, delayed‑plugin, fixed‑level and timestamp‑based approaches—provides detailed architectural diagrams, code samples, scaling strategies, operational checklists, and guidance on choosing the right solution for production workloads.
Delayed MessagingOutbox PatternRabbitMQ
0 likes · 39 min read

The article dissects why message loss is an end‑to‑end engineering challenge across production, broker, and consumer stages, presents real‑world failure cases at ten‑million QPS, and outlines concrete strategies—ack loops, outbox tables, broker replication settings, consumer handling rules, observability, reconciliation, and SLA‑driven compensation—to evolve from best‑effort to provable, recoverable reliability.
ObservabilityOutbox PatternSLA
0 likes · 17 min read

This comprehensive guide compares PostgreSQL and MySQL from an engineering perspective, covering business models, transaction semantics, concurrency, replication, scalability, operational costs, real‑world case studies, and a decision matrix to help teams choose the database that minimizes long‑term complexity and cost.
MySQLOutbox PatternPostgreSQL
0 likes · 38 min read

This comprehensive guide walks through building a production‑grade e‑commerce order service with Spring Boot 3, covering everything from domain modeling and layered architecture to high‑concurrency safeguards, idempotent design, outbox messaging, distributed transactions, caching strategies, observability, security hardening, and cloud‑native deployment on Kubernetes.
Java 17KubernetesMicroservices
0 likes · 44 min read

This article explains the challenges of maintaining data consistency in distributed, event‑driven microservice architectures and introduces three practical patterns—Outbox, Original Event Handling, and Self‑Read—to guarantee reliable state synchronization across services, even when failures occur.
CDCOutbox Patterndistributed-transactions
0 likes · 6 min read


ITPUBDec 24, 2021 · Backend Development
The article explains why the naïve "save‑then‑publish" pattern in message‑driven microservices can cause data inconsistency, analyzes failure scenarios, and presents the local outbox pattern with transactional guarantees and eventual consistency as a robust solution.
Message-DrivenOutbox Patterndistributed-transactions
0 likes · 9 min read
