OrchestratorHost

Remarks

⚠ A library that configures a host, not an executable. Doc 17's model is that the application is the executable and nothing in its boot path is a black box, and an orchestrator is an application like any other: its Program.cs builds a host, calls the one method below, and runs it. What that buys is that an integration test stands the same silo up in-process, and that a deployment which wants a different clustering provider edits its own five lines rather than a configuration schema this package invented.

⚠ Clustering is deliberately not chosen here. Doc 27 ADR-016 lists the providers — Clustering.AdoNet, Clustering.Redis, Clustering.AzureStorage, Hosting.Kubernetes — and picking one would tie the engine to a deployment target the brief explicitly keeps open. UseVixenOrchestrator configures the grains and leaves membership to the caller; UseDevelopmentCluster is the one-line localhost answer for a laptop and says so in its name.

Methods (2)

• public static IHostApplicationBuilder UseVixenOrchestrator(this IHostApplicationBuilder builder, OrchestratorOptions options)

  Registers the orchestrator's grains and what they need.

• public static IHostApplicationBuilder UseDevelopmentCluster(this IHostApplicationBuilder builder, OrchestratorOptions options)

  The localhost clustering a laptop wants, in one line.