Skip to main content
Namastack · Open source · Spring Boot

Your business commits.
Reliability follows.

Keep outgoing work with your business data. Protect incoming operations from duplicates. Focused libraries that make your database transaction a reliable foundation.

Java & KotlinYour databaseApache 2.0Built for Spring Boot

Start at the boundary you need.​

Use either library independently. Combine them when work crosses services.

Transactional outbox1.11.x

Namastack Outbox.

Commit outgoing work with your business data. Deliver it asynchronously, with ordering and retries.

Transactional idempotency0.1.x

Namastack Once.

Commit your business operation and its marker together. Skip duplicate invocations with the same scope and key.

Namastack Outbox

Commit the intent.
Deliver after the commit.​

Save outgoing work beside your business data in one transaction. Outbox delivers it asynchronously, with per-key ordering and retries when a destination recovers.

One transaction. Business data + outgoing work.
@Transactional
public void place(Order order) {
orders.save(order);
outbox.schedule(
new OrderPlaced(order.id()),
order.id().toString()
);
}
Namastack Outbox

Every event matters.

Committed work is delivered at least once. Consumers own their acknowledgement and duplicate handling.

Namastack Once

Accept the retry.
Skip the duplicate.​

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.

Namastack Once

Once. Transactional idempotency.

A local transaction protects the business effect. Remote calls stay outside that boundary.

Better together

Deliver reliably. Commit the effect once.​

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.

  1. 01Business transactionSave data + outgoing work
  2. 02OutboxDeliver with ordering + retries
  3. 03Message brokerCarry the stable event identity
  4. 04OnceReserve + execute + commit
  5. 05Business transactionProtect the local business effect
Understand the combined guarantee →
From an example to your application

A familiar Spring Boot starting point.​

Constructor injection, your database, and application-owned migrations. Explore working examples and bring your questions to the community.

Support the work

Namastack Outbox and Namastack Once are independently developed and maintained as open-source software. Sponsorship supports maintenance, documentation, integrations, and long-term stability.