Performance Database Overview
Summary
Source-backed overview of Performance persistence ownership and verified model totals.
Audience
Backend engineers, database reviewers, architects, QA, support, operations, security reviewers, and product owners.
Overview
Performance uses EF Core with PostgreSQL through one runtime PerformanceDbContext. The context owns canonical aggregates, child entities, history, and messaging-support records. A derived backfill context reuses the same model with transition-specific identifier generation behavior.
Confirmed persistence behavior
- Eight logical persisted object sets and eight logical primary keys are configured.
- Seven owned-value mappings represent four distinct value-object types.
- Two configured aggregate-child foreign keys use cascade deletion.
- Twelve indexes are explicit in context configuration; the snapshot contains fourteen because two relationship-support indexes are convention generated.
- The snapshot contains three unique and eleven non-unique indexes.
- Six logical objects have tenant query filters; delivery and processed-event records do not.
- Two migrations and one current model snapshot exist.
Classification
Implemented persistence model with Transitional compatibility and backfill behavior.
Requires confirmation
Production ownership, retention, archival, recovery targets, concurrency policy, and final system-of-record status require confirmation.
Diagram
Related Articles
See Also
Keywords
- Performance persistence
- Database Overview
- Draft database documentation
Source References
microservices/src/performance-service/Infrastructure/PerformanceDbContext.csmicroservices/src/performance-service/Infrastructure/Persistence.csmicroservices/src/performance-service/performance-service.csprojmicroservices/src/performance-service/Infrastructure/Migrations/PerformanceDbContextModelSnapshot.cs
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly