The Transactional Outbox in Go: Reliable Event Publishing Without Distributed Transactions
Here is one of the oldest bugs in distributed systems, still shipping to production every week: a service commits a
Tag: Outbox Pattern
The Transactional Outbox Pattern in Go: Reliable Events Without Dual Writes
# POST 1: Transactional Outbox (Slot 10 backend) You update a row in your database, then publish an event to
Continue readingThe Transactional Outbox Pattern in Go: Reliable Events Without Dual Writes
The Transactional Outbox Pattern: Reliable Events Without Distributed Transactions
Solve the dual-write problem with one extra table and SKIP LOCKED: a working Go implementation of the transactional outbox, plus the delivery-semantics gotchas that bite in production. … Continue readingThe Transactional Outbox Pattern: Reliable Events Without Distributed Transactions
Dead Letter Queues in Kafka: Stop Poison Pills Before They Stop You
A message arrives that your consumer cannot parse. Maybe the producer shipped a new schema without telling anyone, maybe the
Continue readingDead Letter Queues in Kafka: Stop Poison Pills Before They Stop You
Change Data Capture with PostgreSQL and Debezium: Building Reliable Event Pipelines
Every application that updates a database and then does something else — pushes to a search index, invalidates a cache,
Continue readingChange Data Capture with PostgreSQL and Debezium: Building Reliable Event Pipelines
The Outbox Pattern: Solving the Dual-Write Problem in Event-Driven Microservices
Event-driven architecture is the default for most microservices systems today. Services communicate by publishing events to a message broker —
Continue readingThe Outbox Pattern: Solving the Dual-Write Problem in Event-Driven Microservices