Asset Management Database Documentation
Summary
Complete Draft persistence documentation for the source-backed Asset Management EF Core model: the AssetDbContext, its seven persisted object sets, the Asset aggregate and its children, tenant query filters, the transactional outbox, compatibility identity, migrations, development seeding, and the transitional backfill.
Audience
Backend engineers, database reviewers, architects, QA, support, operations, security reviewers, and product owners responsible for Asset Management data.
Overview
Asset Management persists through one runtime AssetDbContext (Npgsql / PostgreSQL, EF Core 8), a derived backfill context that reuses the same model with transition-specific identity generation, and a design-time context factory. The verified model contains seven persisted object sets across seven tables, seven Guid primary keys, two aggregate-child foreign keys (both cascade), four owned value-object mappings, five tenant query filters, fourteen non-primary-key indexes in the model snapshot, and one authored migration.
The implementation remains Transitional because compatibility identity and backfill paths coexist with canonical persistence, and because production governance, concurrency, retention, and final system-of-record ownership require confirmation.
Documentation map
- Database Overview
- Persistence Architecture
- Ownership and Boundaries
- DbContext and Object Sets
- Asset Storage
- Assignment History Storage
- Document Reference Storage
- Workflow Reference Storage
- Compatibility Identity Storage
- Audit and Timeline Storage
- Outbox Storage
- Processed Event Storage
- Tenant Isolation
- Entity Mappings
- Keys and Relationships
- Indexes and Constraints
- Value-Object Conversions
- Query Patterns
- Data Integrity
- Transactions and Save Boundaries
- Concurrency
- Migrations and Snapshot
- Development Seeding
- Compatibility Backfill
- Retention and Cleanup
- Database Testing Guide
- Schema Reference
- Database Limitations
- Source Map
Requires confirmation
Production ownership, migration governance, retention, recovery, concurrency policy, tenant access exceptions, compatibility retirement, reconciliation sign-off, and final system-of-record status require confirmation.
Source References
microservices/src/asset-service/Infrastructure/AssetDbContext.csmicroservices/src/asset-service/Infrastructure/Persistence.csmicroservices/src/asset-service/Domain/Asset/Asset.csmicroservices/src/asset-service/Infrastructure/Migrations/AssetDbContextModelSnapshot.csmicroservices/src/asset-service/Backfill/AssetRecordBackfill.csmicroservices/scripts/smoke-asset.ps1
Related Articles
See Also
Keywords
- Asset persistence
- EF Core
- Database documentation
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly