Skip to content

Outbox abstractions, schema and migrations #28

Closed
2 of 2 issues completed
Closed

Description

@thomhurst

Foundations of the outbox (design §6.3, decision D12).

Scope

  • Store abstraction used by the dispatcher.
  • Tables: outbox, outbox_dead, inbox, leases, with the indexes in design §6.3 (filtered or partial where the database supports it).
  • Configurable schema and table prefix.
  • Ship SQL scripts per database and a dotnet relayer db script --provider <name> command.

Acceptance criteria

  • Scripts are idempotent and tested against real databases.

Foundation shipped: #5 in #70 provides scoped send execution and IOutboxEnlistment hooks. This issue still implements the durable store abstraction, schemas, idempotent database scripts and script command; EF Core transaction enlistment remains in #29.

See docs/design.md and docs/decisions.md.

Health adapter acceptance criteria (follow-up to #98)

Activity

  1. thomhurst commented on Nov 1, 2026

    @thomhurst
    OwnerAuthor

    Triage against origin/main 66f3349: #5 shipped in #70 with send execution and IOutboxEnlistment hooks. Updated the body to distinguish that foundation from the remaining durable store/schema/script work. No open prerequisite remains; EF Core transaction enlistment stays in #29.

  2. thomhurst commented on Nov 1, 2026

    @thomhurst
    OwnerAuthor

    Split the remaining foundation into native sub-issues #108 (durable dispatch contracts and optional keyed health adapter) and #109 (PostgreSQL schema, idempotent scripts, CLI and real database threshold fixtures). #109 is blocked by #108. The other database providers remain in #41. I am implementing #108 first; #28 stays open until both deliverables ship.

  3. added and removed on Nov 1, 2026
  4. thomhurst commented on Nov 1, 2026

    @thomhurst
    OwnerAuthor

    Verified the remaining parent acceptance criteria against freshly fetched origin/main at 541c460. Both native sub-issues are closed and their implementations are merged:

    This completes the parent scope established in the split comment. SQL Server/MySQL remain #41; EF Core transaction enlistment remains #29 and the PostgreSQL store implementation remains #30. No additional implementation is required for #28.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions