Asset Gateway Boundaries
Summary
The gateway is an HTTP routing surface in front of asset-service. It participates in no part of the asset event model and produces or consumes no integration contract.
Audience
Engineering, integration, QA, architecture, and security reviewers.
Reference Content
Routing, not eventing
The gateway forwards HTTP requests to asset-service endpoints (including the compatibility endpoints). It does not publish, subscribe to, or transform asset events. No event contract crosses the gateway; the gateway sees only HTTP requests and responses.
What flows where
| Concern | Path | Event? |
|---|---|---|
| Frontend and monolith HTTP requests | Gateway to asset-service endpoints | No |
| Asset lifecycle events | asset-service outbox to shared event bus to Notification | Yes |
| Outbox diagnostics read | Gateway to asset-service read endpoint | No |
Correlation continuity
Correlation identifiers set on inbound HTTP requests can be propagated into the events emitted by the resulting operation (the outbox row carries a CorrelationId). The gateway itself neither creates nor terminates events; it only carries the HTTP request that triggers them. See Ordering and correlation.
Public-safety note
Gateway routes, hosts, and ports are intentionally excluded.
Source References
microservices/src/asset-service/Api/AssetEndpoints.csmicroservices/src/asset-service/Program.cs
Related Articles
See Also
Keywords
- Gateway boundary
- Routing
- Not an event
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly