BitzOrcas.Modern separates runtime concerns into dedicated Host composition roots: synchronizing HTTP APIs, edge gateways, and background workers while sharing telemetry via ServiceDefaults.
Host Composition Topology
Host Responsibility Matrix
| Host Project | Default Port | Core Responsibilities & Architecture Positioning |
|---|---|---|
BitzOrcas.Api | 6883 (HTTPS) / 6881 (HTTP) | Primary business API host, executing JWT/2FA authentication, tenant resolution, 10-stage pipeline execution, and vertical slice handler dispatch |
BitzOrcas.Gateway | 6880 (HTTP) | YARP reverse proxy gateway, handling global rate limiting, CORS security headers, and domain routing |
BitzOrcas.JobHost | No external HTTP port | Quartz distributed background worker host, executing data archival, subscription renewal deductions, and unfulfilled ticket timeouts |
BitzOrcas.AppHost | 6888 (Dashboard) | .NET Aspire local orchestration composition root, bootstrapping containers and micro-kernel instances with integrated distributed tracing |
Summary
Clear host responsibility boundaries provide operational elasticity:
- Traffic Surge Isolation: The gateway tier absorbs and throttles burst traffic, safeguarding internal business APIs;
- Asynchronous Task Decoupling: Heavy data archival and reporting workloads run in
JobHost, never competing for API request thread pools.