Getting Started
View on GitHub
Welcome!
Why should you use Namastack Outbox for Spring Boot?
-
Reliable Event Delivery
Ensure each event is delivered at least once, even if failures occur. Retries and transactional storage guarantee no events are lost.
-
Consistent State and Messages
Keep your database and message broker in sync by storing events within the same transaction as your business data.
-
Asynchronous Scalability
Offload message publishing to a background process, allowing your main workflow to remain fast and responsive.
-
Simple and Transparent
Designed for simplicity — no complex infrastructure required. Just use your database and a reliable message dispatcher.
-
Observability and Monitoring
Track the status of your outbox events and failures with metrics, logs, and dashboards, making it easier to debug and operate reliably.
-
Transactional Safety
Outbox ensures your business operations are atomic — either both the database update and message dispatch succeed, or neither does.
How It Works
Namastack Outbox for Spring Boot brings bulletproof reliability to your event-driven systems — combining transactional integrity with seamless message delivery.
When your application writes data, both the entity table and the outbox table are updated within a single ACID transaction. This guarantees that your domain state and outgoing events are always consistent — even if the system crashes mid-operation.
A background outbox scheduler polls the database for new outbox records and hands them off to your custom outbox processor — a lightweight interface you implement to publish messages to your broker (e.g. Kafka, RabbitMQ, SNS).
Once messages are successfully delivered, they’re marked as processed.
This architecture ensures:
- Zero message loss, even under failure
- Strict per-aggregate ordering for deterministic processing
- Horizontal scalability with distributed locking
- At-least-once delivery with safe retry policies and observability
With Namastack Outbox for Spring Boot, you get the reliability of database transactions — and
the resilience of message-driven design.
Build confidently, scale safely, and never lose an event again.