Namastack Outbox.
Commit outgoing work with your business data. Deliver it asynchronously, with ordering and retries.
Keep outgoing work with your business data. Protect incoming operations from duplicates. Focused libraries that make your database transaction a reliable foundation.
Use either library independently. Combine them when work crosses services.
Commit outgoing work with your business data. Deliver it asynchronously, with ordering and retries.
Commit your business operation and its marker together. Skip duplicate invocations with the same scope and key.
Save outgoing work beside your business data in one transaction. Outbox delivers it asynchronously, with per-key ordering and retries when a destination recovers.
@Transactional
public void place(Order order) {
orders.save(order);
outbox.schedule(
new OrderPlaced(order.id()),
order.id().toString()
);
}
Committed work is delivered at least once. Consumers own their acknowledgement and duplicate handling.
Retries are part of delivery. Give each operation a stable identity, commit its marker with your business writes, and skip work that already succeeded.
@Idempotent(scope = "orders.create")
public void create(@IdempotencyKey UUID requestId) {
orderService.create(requestId);
}
Once owns the transaction. Invoke this boundary outside an existing transaction.
A local transaction protects the business effect. Remote calls stay outside that boundary.
Outbox delivers committed work at least once. Once protects the receiving service’s local transaction. Preserve the event identity and retain its marker across retries to keep repeated delivery from repeating a committed business effect.
Constructor injection, your database, and application-owned migrations. Explore working examples and bring your questions to the community.
Namastack Outbox and Namastack Once are independently developed and maintained as open-source software. Sponsorship supports maintenance, documentation, integrations, and long-term stability.