Skip to main content

Expense Migrations and Seeding

Summary​

The confirmed migration sequence is:

Audience​

Backend developers, database reviewers, QA, architects, DevOps, support, and implementation teams.

Confirmed persistence​

The confirmed migration sequence is:

  1. Initial Expense persistence: claims, receipt references, audit, timeline, outbox, processed-event ledger, relationships, and indexes.
  2. Receipt storage metadata expansion.
  3. Approver remarks addition.

A current model snapshot represents the expected EF model. Development startup can apply migrations and invoke idempotent sample seeding. A confirmed startup guard suppresses both actions when enabled; its configuration control is intentionally omitted from public documentation. Production migration execution is not embedded in the confirmed startup path.

Seed data is development-only and exercises Pending, Approved, and Rejected aggregate paths, including outbox creation. Migration approval, production ownership, rollback testing, and snapshot governance require confirmation.

Requires confirmation​

Production migration governance, retention, archival, masking, performance targets, concurrency roadmap, operational-store access, and rollback ownership remain unconfirmed unless narrowed above.

Source References​

  • microservices/src/expense-service/Infrastructure/Migrations/20260706184830_InitialExpenseSchema.cs
  • microservices/src/expense-service/Infrastructure/Migrations/20260706200904_AddReceiptStorageFields.cs
  • microservices/src/expense-service/Infrastructure/Migrations/20260707062634_AddApproverRemarks.cs
  • microservices/src/expense-service/Infrastructure/DevelopmentSeeder.cs
  • microservices/src/expense-service/Program.cs

See Also​

Keywords​

  • Expense database
  • Migrations and Seeding

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-16
  • Review cycle: Quarterly