Skip to content

STORY: Publish ledger posting completion events #101

Closed
1 of 1 issue completed
Closed

Description

@ramioooz

Type: Story
Epic: Ledger and Financial Posting
Slice: Slice 7 - Events + Notification
Service: ledger-service
Priority: P0

Publish ledger posting lifecycle events that drive account balance projection and transfer status changes.

Scope:

  • Define LedgerPostingCompleted and LedgerPostingFailed events.
  • Publish events through a transactional outbox, not directly from request handlers.
  • Include posting id, transaction id, account ids, amounts, currency, event id, causation id, and correlation id.
  • Define partitioning and ordering expectations.

Definition of Done:

  • Ledger events are emitted only after durable ledger state changes.
  • Outbox publication is retryable and idempotent.
  • Events contain enough information for Account Service and Transaction Service consumers.
  • Failure and dead-letter handling expectations are documented.

Activity

  1. added theissue type on Aug 2, 2026
  2. self-assigned this
    on Aug 30, 2026
  3. ramioooz commented on Sep 1, 2026

    @ramioooz
    MemberAuthor

    Sprint 3 completion evidence: Ledger Service PRs #14, #15, and #16 are merged. They implement the transactional posting outbox, governed completion/failure publication, retry/quarantine delivery, and lease/idempotency hardening. Their PR verification reports Maven verify plus PostgreSQL/Testcontainers coverage. Child task #170 is complete; Kafka consumers and account/transfer integration remain in Sprint 3 stories #102 and #103.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions