Asset Management Technical Documentation

Summary

Asset Service is a .NET 8 ASP.NET Core minimal-API process with one web project and folder-level API, Application, Domain, Infrastructure, Messaging, Compatibility, and Backfill separation. It owns a typed aggregate, tenant-scoped EF Core persistence, audit/timeline evidence, document references, optional workflow approval, and a transactional lifecycle-event outbox.

Audience

Engineering, QA, support, operations, architecture, security, and implementation teams.

Overview

The implementation is Transitional. A dedicated service and direct API exist, while gateway feature-controlled cutover, monolith-shaped compatibility routes, and legacy employee identifiers remain. Authentication is registered, but mapped asset endpoints do not require authorization policies.

Documentation covers architecture, runtime, structure, layers, domain, aggregate, application, persistence, messaging, integrations, security context, observability, testing, limitations, and the source map.

Requires confirmation

Production authorization policy, infrastructure ownership, service objectives, operational dashboards, retention, test-suite ownership, and compatibility retirement criteria require confirmation.

Source References

• microservices/src/asset-service/Program.cs
• microservices/src/asset-service/asset-service.csproj
• microservices/src/asset-service/Domain/Asset/Asset.cs
• microservices/src/asset-service/Infrastructure/AssetDbContext.cs

Related Articles

• Asset Management
• Business documentation

See Also

• Technical limitations
• Technical source map

Keywords

• Asset Service architecture
• Asset aggregate
• Transactional outbox

Revision Information

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