Hosting Capability Catalog

LiteBus hosting capabilities define how modules become running workloads. Runtime modules register service dependencies and host manifest entries during composition. Host adapters map the manifest to Generic Host lifecycles, ASP.NET Core endpoints, and OpenTelemetry registration.

The axis is intentionally split into small packages. Composition (AddLiteBus) stays separate from host bridges, management HTTP endpoints, health checks, and telemetry registration.

Manifest Model

AddLiteBus(...)
  -> module registry resolves build order
  -> modules register dependencies and manifest entries
  -> LiteBusHostManifest snapshot is registered
  -> host bridges resolve startup tasks, background loops, diagnostic checks
  -> optional ASP.NET health and management endpoints consume the same manifest

Manifest entry contracts:

• IStartupTask: one-shot startup work
• IBackgroundService: long-running loop work
• IDiagnosticCheck: framework-neutral readiness probes

Startup tasks run first. Background loops start only after startup tasks complete. Any startup task failure fails host startup.

Capabilities (16)

Package Boundaries

• Platform, mediation, durable, core, technology, and feature roles register manifest entries without referencing host frameworks directly.
• Host-adapter packages bridge the manifest to IHostedService, ASP.NET endpoints, or OpenTelemetry builders.
• Apps remain responsible for authentication, authorization policy, rate limiting, and exporter setup.

Test Sources

Deep Docs

• Hosted services
• Diagnostics and health
• Architecture
• Dependency graph