Asset Operations Overview
Summary
This page orients operators to how the asset-service runs and how it connects to the wider HR Suit platform. The asset-service is an ASP.NET Core (net8.0) minimal API that owns the asset schema and exposes foundation, compatibility, and diagnostic endpoints. It integrates with the gateway (YARP), workflow-service, document-service, and notification-service, and publishes domain events through a transactional outbox. This overview links to the detailed operations pages and states the operational posture and known boundaries.
Audience
- DevOps engineers running or deploying the asset-service.
- Developers integrating with or extending asset operations.
- Support and QA engineers triaging runtime behavior.
- Solution and security architects assessing boundaries and posture.
Reference Content
Operational scope
The asset-service is a bounded-context microservice within the platform's transitional monolith-to-microservices migration. During transition it can serve the asset slice directly or defer to the monolith, controlled by a gateway feature flag (see gateway and compatibility operations).
Operational context
Subsystem map
| Subsystem | Role in asset operations | Detail page |
|---|---|---|
| Runtime and startup | Host boot order, middleware pipeline, dev-only migrate/seed | See runtime and startup |
| Health and diagnostics | Liveness, service-info, tenant health-data | See health and diagnostics |
| Outbox and messaging | Event staging and relay to the broker | See outbox and messaging operations |
| Workflow | Feature-flagged approval integration | See workflow operations |
| Document | Reference-only document integration | See document operations |
| Notification | Downstream consumer of asset events | See notification operations |
| Gateway and compatibility | Routing flag, shadow route, ESS composition | See gateway and compatibility operations |
Security posture boundary
Foundation, native, and compatibility endpoints are anonymous and tenant-scoped by design for the private service mesh. JWT bearer authentication is configured but endpoints are not role-authorized. This is a documented posture and an operational boundary, not a defect addressed here.
Source References
microservices/src/asset-service/Program.csmicroservices/src/gateway-api/Program.cs
Related Articles
See Also
Keywords
asset operations, asset-service runtime, operational boundaries, gateway routing, transitional migration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly