Tagged articles
Order Service
13 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

The article demonstrates why distributed locks alone fail to guarantee idempotency in Spring Boot order APIs, and presents a three-layer solution combining Idempotency-Key with request fingerprinting, Redis SET NX for fast duplicate interception, and a database unique constraint as the ultimate safeguard against duplicate orders even after crashes or Redis failures.
API DesignDistributed LocksIdempotency
0 likes · 25 min read

This article explains how to build a robust order service using Seata distributed transactions, Redisson distributed locks, CompletableFuture for asynchronous operations, token-based duplicate‑submission prevention, and RabbitMQ delayed queues for automatic order cancellation, with full Java code examples.
Distributed LockOrder ServiceSeata
0 likes · 21 min read

This article provides a comprehensive technical deep‑dive into a modular transaction system for large‑scale membership services, covering its architecture, core workflow, component design, configuration details, order and signing services, product handling, settlement process, and stability mechanisms.
Order Servicebackend designclearing settlement
0 likes · 18 min read

This article explains how to achieve idempotent order creation and updates by using unique request identifiers, database primary‑key constraints, Redis flags, and a version‑column strategy to prevent duplicate submissions and resolve the ABA anomaly in distributed systems.
ABA problemBackendIdempotency
0 likes · 12 min read

This article explains how to achieve idempotent order creation and updates by using unique request identifiers, database primary‑key constraints, Redis flags, and optimistic locking with version columns, thereby preventing duplicate orders and solving the ABA problem in distributed backend systems.
ABA problemIdempotencyOrder Service
0 likes · 11 min read

This article explains how to achieve idempotent order creation and updates in backend services by using database transactions, unique request identifiers, Redis flags, and optimistic locking with a version column to prevent duplicate submissions and solve the ABA problem.
ABA problemIdempotencyOrder Service
0 likes · 10 min read

This article explains how to achieve idempotent order creation and updates in backend services by using unique request identifiers, database unique constraints, Redis flags, and optimistic locking with version columns, while also addressing the ABA problem with practical code examples and diagrams.
ABA problemIdempotencyOrder Service
0 likes · 10 min read

This article explains how to prevent duplicate order submissions and address the ABA concurrency issue by using database transactions, unique constraints, request identifiers, and version‑based optimistic locking to achieve reliable idempotent behavior in backend order services.
ABA problemDatabase TransactionOrder Service
0 likes · 10 min read

The article explains how to achieve idempotent order creation and update operations by using unique request identifiers, database primary‑key constraints, Redis flags, and version columns to prevent duplicate submissions and resolve ABA anomalies in distributed backend systems.
ABA problemBackendIdempotency
0 likes · 10 min read

This article explains how to build a highly reusable shared order service by clearly defining its boundaries, abstracting its internal data model and interfaces, and handling order status management with both main and sub‑status mechanisms, while avoiding tight coupling with other services.
Order Servicebackend architecturemicroservice
0 likes · 15 min read


JavaEdgeAug 17, 2020 · Backend Development
This article explains how to keep order services consistent across distributed systems by using database transactions, unique primary‑key constraints for idempotent order creation, and optimistic‑locking version fields to avoid duplicate orders and solve the ABA problem.
ABA problemBackendDatabase Transaction
0 likes · 10 min read

This article describes how Ctrip's ticket order post‑service team identified scaling bottlenecks, selected Redis, designed a two‑level cache architecture, implemented active and passive caching strategies, tackled consistency and failure issues, and applied various optimizations to achieve over 90% cache hit rate and dramatically reduce database load.
CacheCtripOrder Service
0 likes · 14 min read
