Tagged articles

transactional outbox

9 articles · Page 1 of 1
Data Bricklaying Diary
Data Bricklaying Diary
Sep 25, 2026 · Backend Development

From Table-Driven to Ontology-Driven: Why Data Alone Can't Explain Business

This article argues that ontology-driven modeling — defining business concepts like delivery, deferral, and confirmation — enables AI and humans to trace actual order records, distinguish occurred facts from pending requests and causal guesses, and answer why an order was delayed without full system rewrite or event sourcing.

AI explanationbusiness modelingdata semantics
0 likes · 17 min read
From Table-Driven to Ontology-Driven: Why Data Alone Can't Explain Business
Cloud Architecture
Cloud Architecture
Sep 17, 2026 · Databases

Indexes Aren't Free: Production Index Governance for High-Write Order Systems

This article presents a comprehensive index governance methodology for high-write MySQL order systems, demonstrating through a real incident how a read-optimized index caused write latency, replica lag, and timeouts, and detailing a reusable process covering query-driven design, cost measurement, validation, change buffer limits, index convergence, safe deletion, read-write routing, sharding, transactional outbox, idempotent consumers, online DDL safeguards, gating, and long-term ownership.

Capacity PlanningChange BufferDescending Indexes
0 likes · 29 min read
Indexes Aren't Free: Production Index Governance for High-Write Order Systems
Ray's Galactic Tech
Ray's Galactic Tech
Aug 20, 2026 · Backend Development

Payment Reconciliation: Detecting Lost Orders, Over‑payments and Auto‑Repairing Them

The article explains why successful payment does not guarantee correct accounting, defines discrepancy types such as lost orders, over‑payments and shortfalls, and presents a production‑grade reconciliation architecture with T+1 bill ingestion, shard‑based diff detection, state‑machine driven error handling, automatic repair workflows, and comprehensive monitoring.

auto-repairlost ordersmonitoring
0 likes · 45 min read
Payment Reconciliation: Detecting Lost Orders, Over‑payments and Auto‑Repairing Them
Ray's Galactic Tech
Ray's Galactic Tech
Aug 14, 2026 · Backend Development

Payment Callback After Order Cancellation? 3 Consistency Challenges and Practical Engineering Solutions

The article examines why payment callbacks that arrive later than order cancellations cause money‑in‑order‑canceled anomalies, outlines the three core eventual‑consistency problems—message ordering, duplicate consumption, and message loss—and presents a complete engineering solution using business idempotency keys, a transactional outbox, state‑machine handling, and reconciliation compensation.

IdempotencyKafkadistributed systems
0 likes · 35 min read
Payment Callback After Order Cancellation? 3 Consistency Challenges and Practical Engineering Solutions
Random Bulletin
Random Bulletin
Jul 17, 2026 · Backend Development

Ten‑Million QPS Architecture: From Strong to Eventual Consistency with Layered Design

The article examines why ultra‑high‑throughput systems must move from costly strong consistency to eventual consistency, explaining consistency layering, the trade‑offs of coordination latency, availability, and tail latency, and how local message tables, idempotent delivery, compensation (Saga) and periodic reconciliation together ensure data eventually aligns without sacrificing performance.

SAGAcompensationconsistency
0 likes · 17 min read
Ten‑Million QPS Architecture: From Strong to Eventual Consistency with Layered Design
Tinker Programmer
Tinker Programmer
Jul 1, 2026 · Backend Development

How Domain Events Decouple Communication Between Bounded Contexts

The article analyzes the pitfalls of synchronous calls in a payroll microservice, defines domain events and their naming conventions, compares them with message‑queue messages, and presents two concrete implementations—Spring ApplicationEvent for intra‑process decoupling and RocketMQ with a transactional outbox for cross‑process communication—while also clarifying when event sourcing is appropriate.

DDDDomain EventsRocketMQ
0 likes · 15 min read
How Domain Events Decouple Communication Between Bounded Contexts
Java Web Project
Java Web Project
Apr 14, 2026 · Backend Development

Why Seata’s Global Locks Can Kill High‑QPS Services—and What to Do Instead

The author recounts 18 months of using Seata for distributed transactions, explains its three‑role architecture and AT mode, details how global locks caused severe latency and deadlocks under load, and shows how switching to a transactional outbox pattern restored performance and eliminated the undo_log bloat.

Seatadistributed transactionsmicroservices
0 likes · 8 min read
Why Seata’s Global Locks Can Kill High‑QPS Services—and What to Do Instead
Full-Stack Internet Architecture
Full-Stack Internet Architecture
May 19, 2021 · Backend Development

Understanding Message Queues: Benefits, Design Challenges, and Transactional Solutions

This article explores the role of message queues in microservice architectures, discussing their advantages such as decoupling, asynchronous processing, and load shedding, while also addressing design challenges like concurrency, ordering, duplicate handling, and transactional messaging with solutions including Kafka partitions, outbox patterns, CDC, and RocketMQ.

CDCKafkaRocketMQ
0 likes · 12 min read
Understanding Message Queues: Benefits, Design Challenges, and Transactional Solutions