Skip to content

TASK: Implement Account Service reservation command and fact transport #183

Closed

Description

@ramioooz

Type: Task
Parent: #102
Epic: Sprint 3 - Internal Transfers and Event Consistency
Service: account-service
Priority: P0

Objective

Implement Account Service transport for reservation commands and governed reservation outcome events.

Scope

  • Consume AccountReservationRequested.v1 and AccountReservationReleaseRequested.v1.
  • Delegate command handling to the existing reservation application services.
  • Persist destination account identity where required by the governed accepted/rejected facts.
  • Publish AccountReservationAccepted.v1, AccountReservationRejected.v1, AccountReservationReleased.v1, and AccountReservationExpired.v1 through a transactional durable outbox.
  • Add event inbox deduplication, validation, retry, and dead-letter/quarantine behavior.
  • Keep Kafka disabled by default and enable only through explicit SIT configuration.
  • Preserve optimistic locking, reservation idempotency, and ledger-driven balance changes.

Acceptance criteria

  • Duplicate commands and facts are safe across retries and restarts.
  • Conflicting event identity reuse is rejected without a second state transition.
  • Reservation state and corresponding outbox fact commit atomically.
  • Expiry and ledger failure produce exactly one governed fact.
  • Invalid headers and payloads cannot corrupt account state.
  • ./mvnw verify passes.

Dependencies

This task must remain under parent story #102 and Sprint 3. Implement through a non-draft PR. Do not merge directly to main.

Activity

  1. self-assigned this
    on Aug 31, 2026
  2. ramioooz commented on Sep 1, 2026

    @ramioooz
    MemberAuthor

    Completed by merged Account Service PR #36. The PR implements reservation command/fact transport, durable inbox/outbox state, transport metadata preservation, and focused verification. No deployment delay is required before the next SIT rollout.

  3. added theissue type on Sep 4, 2026
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