Design a Transactional Outbox · System Design Interview

Design a Transactional OutboxDesign how a service that has just committed a row publishes the event about it, so the row and the event cannot disagree.What it has to do

Every committed change produces exactly one published event

A change that is rolled back publishes nothing

Events for the same entity are published in the order they were committed

Scale

Committed changes per second: 150,000

Services publishing this way: 400

Out of scope

The consumers of the events

Schema evolution of the event payload

The broker’s own durability

Practise this challengeAll system design challenges

LetsDiscuss

Loading your session…