Durable Core Capability Catalog
LiteBus durable messaging persists commands and events before execution or publication, then replays them through background processors with at-least-once delivery, leases, retries, and operator tooling. This catalog maps each capability to its public surface, packages, invariants, observability, and test coverage.
Scope: inbox, outbox, reliable semantics, transactional writes, domain events, command-inbox patterns, envelope lifecycle, processors, lease/retry/dead-letter, idempotency, and scheduling metadata. Broker-specific transport guides live outside this axis; dispatch and ingress capabilities here describe how durable core connects to transport adapters.
Catalog sections (per capability file):
| Section | Content |
|---|---|
| Public surface | Consumer contracts, invocation, registration, configuration, and extension points (replaces legacy Entry APIs tables) |
| Observability | Per-instrument detail: name, kind, when emitted, tags, enablement, operational notes |
| Test coverage | One block per automated test method (use case, kind, description, behavior, outcome, remarks); untested and out-of-scope gaps remain as tables |
Test coverage research: Tests under tests/LiteBus.Inbox.UnitTests, tests/LiteBus.Outbox.UnitTests, tests/LiteBus.Durable.IntegrationTests (Ingress/, Dispatch/, Registration/), tests/LiteBus.Enterprise*, and tests/LiteBus.Storage*.
Maturity legend
| Tier | Meaning |
|---|---|
| GA | Production-ready; stable public contract |
| Beta | Shipped; exercise in non-critical paths first |
| Extension | Optional package on top of durable core |
| Planned | Documented on Roadmap; not shipped |
Capabilities
Deep Docs
| Topic | Doc |
|---|---|
| Inbox reference | Inbox |
| Outbox reference | Outbox |
| Delivery guarantees | Reliable messaging semantics |
| Atomic domain + store | Transactional messaging writes |
| Domain events pattern | Domain events and unit of work |
| Architecture | Architecture (durable sections) |
| Roadmap | Roadmap |