The Transactional Outbox Pattern is well-known, but production details like ordering semantics, scaling, and retry strategies often get overlooked. Namastack Outbox addresses these hard parts with a clear focus on reliability under real load and failures.

Instead of chasing global ordering, it uses key-based ordering (e.g., per `order-123`) with hash-based partitioning across 256 fixed partitions. This enables concurrent processing for different keys while preserving sequence for the same key, avoiding lock contention during scaling.

For outages, it employs configurable exponential backoff retries and fallback handlers. When retries are exhausted, records transition to a `FAILED` state for alerting or dead-letter processing, giving teams a deterministic path for permanently failed records.