Apr 5 · 22 min read · TLDR: Any service that writes to a database and publishes a message in the same logical operation has a dual write problem. try/catch retries don't fix it — they turn failures into duplicates. The Transactional Outbox pattern co-writes business data ...
Join discussionFeb 12 · 11 min read · Why Traditional Event Publishing Fails at Scale The naive approach to event publishing looks deceptively simple: execute a database transaction, then publish an event to your message broker. This dual write creates a fundamental race condition with f...
Join discussionFeb 12 · 10 min read · Metadata SEO Title: Transactional Outbox Pattern for Event-Driven Systems Meta Description: Learn how the Transactional Outbox Pattern solves dual-write problems in event-driven microservices with production-ready TypeScript examples. Primary Keyword...
Join discussionJan 10 · 3 min read · In the previous article, we explored the Outbox Pattern to guarantee that events are published reliably from a producer service. But publishing events safely is only half of the problem. 👉 What happens on the consumer side ? What if the same Kafka ...
Join discussionJan 7 · 5 min read · In a modern microservices architecture, services must communicate asynchronously, decoupled, and reliably. Apache Kafka has become a standard for event transport, but naive usage hides a major risk. 👉 How can we ensure that a Kafka event always repr...
Join discussionSep 26, 2025 · 6 min read · In the world of microservices and distributed systems, communicating and sharing data between different services is a fundamental necessity. But what happens when a service needs to update its own database and, at the same time, notify other services...
Join discussion
Sep 22, 2025 · 6 min read · Since I’m currently preparing for job interviews, I’ve been reviewing materials on application design, including microservice architecture. I noticed that most resources on microservice design patterns usually cover things like: API Gateway Service...
Join discussion
Aug 7, 2025 · 3 min read · Ever built a system where you: Save something to the database Then fire off an event (e.g. send an email or publish to RabbitMQ) And then you pray it doesn’t fail between the DB save and the publish? Yeah. That’s the problem the Outbox Pattern s...
Join discussionJul 5, 2025 · 4 min read · When trying to build resilient and scalable microservices, I’ve often found myself grappling with the problem of ensuring consistency between in memory domain events and external communication such as messaging or database writes. In early attempts, ...
Join discussion
Jun 13, 2025 · 3 min read · The Fantasy of Distributed Systems You built your distributed system, hooked it up to Kafka or NATS or RabbitMQ, and now everything talks to everything else like some perfectly choreographed dance. At least that's what the architecture diagram sugges...
Join discussion
