Expense Deployment and Startup

Summary

Startup registers shared observability and messaging, persistence, integrations, commands/queries, authentication, the hosted outbox relay, endpoints, and health. Confirmed automatic migration/seeding behavior is environment-scoped and suppressible.

The container artifact is Foundation evidence, not a complete public production deployment procedure. Production migration approval, rollback, readiness sequencing, and dependency checks require operator governance.

Requires confirmation

Deployment platform, replica coordination during migration, readiness criteria, release rollback, and production seeding policy require confirmation.

Source References

• microservices/src/expense-service/Program.cs
• microservices/src/expense-service/Infrastructure/DevelopmentSeeder.cs
• microservices/src/expense-service/Infrastructure/Persistence.cs
• microservices/src/expense-service/Dockerfile

Related Articles

• Expense operations documentation
• Expense troubleshooting
• Expense technical documentation

See Also

• Expense events
• Expense module

Keywords

• Expense operations
• Deployment and Startup

Revision Information

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