Outbox table
An outbox table is a persistent database table that stores messages, events, or work items for subsequent processing or delivery.
Grokking Software Architecture
An outbox table is a database table that stores messages or events for later delivery by a separate process.
- How it is used
- Uses a local table and separate process to safely publish events or synchronize data across distributed services.
- How deep it goes
- Explains the shared database transaction and background relay, but does not detail relay implementation.
- Examples
- Uses an InventoryService saving an InventoryDeducted event before a background process forwards it.
- What you can do after
- Apply it to publish events reliably by saving them with business data and relaying them afterward.
Read how Grokking Software Architecture explains outbox table →
Microservices Patterns, Second Edition
An outbox table is a persistent table that stores messages to be delivered reliably as part of an application's transaction.
- How it is used
- Preserves atomic message recording alongside business-data changes when a service must publish through a broker.
- How deep it goes
- Explains local transaction semantics and relay choices, while identifying efficient discovery of pending NoSQL messages as a challenge.
- Examples
- Uses an order service that stores a pending order and validates it asynchronously through consumer and restaurant services.
- What you can do after
- Build it from scratch by inserting messages in the business-data transaction and relaying them to a broker.
Read how Microservices Patterns, Second Edition explains outbox table →
Also covered in
- Clean Applications with Hexagonal ArchitectureIn early access (MEAP)
- Apache Kafka in Action
- Kafka for Architects
What to know first
- message brokerA message broker is intermediary software that receives, routes, and delivers messages between communicating components or systems.
- ACIDACID is the set of database transaction properties—atomicity, consistency, isolation, and durability—that characterize reliable transactional behavior.
- CDCChange data capture is a technique for detecting and recording changes to data in a source system so they can be processed or propagated to other systems.
- distributed transactionA distributed transaction is a unit of work involving multiple independent resources or systems whose outcome is coordinated as a single transaction.
Related concepts
- outbox patternused by · The outbox pattern records an outgoing message or event in the same transaction as an associated data change, then delivers it separately after the transaction commits.
- polling publisherused by · A polling publisher is a messaging pattern in which a separate process periodically queries an outbox for unpublished messages and sends them to a broker.
- database transactionpart of · A database transaction is a bounded unit of database operations whose changes are treated as one logical whole, typically committed or rolled back together.
- CDCuses · Change data capture is a technique for detecting and recording changes to data in a source system so they can be processed or propagated to other systems.
- outbound portused by · An outbound port is an application-facing interface that declares a service or resource the application requires from an external provider.
Questions about outbox table
What is outbox table?
An outbox table is a persistent database table that stores messages, events, or work items for subsequent processing or delivery.
Which Manning books explain outbox table?
Grokking Software Architecture and Microservices Patterns, Second Edition.
What should I know before learning outbox table?
Manning books that teach outbox table usually introduce message broker, ACID, CDC and distributed transaction first.
What is outbox table a kind of?
Outbox table is a kind of table. A table is a data structure that organizes values into rows and columns.
What is outbox table part of?
Outbox table is part of database transaction. A database transaction is a bounded unit of database operations whose changes are treated as one logical whole, typically committed or rolled back together.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

