Package guidance

Use the smallest package set that fits your composition model.

Thresh is intentionally modular: start from core runtime primitives, then add optional packages only where they add clear value.

Install Thresh.Extensions first.

It provides DI registration and the core runtime surface:

  • ILcuHttpClient
  • IEventStream
  • resilience wiring (retry + circuit-breaker)
  • authentication/safety pipeline
  • observability hooks

Package selection

Package Use when Includes
Thresh.Extensions You want the core runtime stack with DI registration ILcuHttpClient, IEventStream, retries, auth handler, observability wiring
Thresh.Endpoints You want typed endpoint groups over ILcuHttpClient Summoner, gameflow, champ select, and lobby typed clients
Thresh.Hosting You run Thresh inside hosted/background processes Hosting integration and lifecycle-friendly wiring
Thresh.HealthChecks You expose readiness/liveness probes LCU health check integration
Thresh.Reactive You prefer reactive composition over callbacks Rx-friendly wrappers around stream events

Composition boundary

Keep business workflows in consumer code.

Thresh intentionally focuses on transport, discovery, and event primitives. It does not provide high-level orchestration or app-level workflows.

Typical progression

  1. Start with Thresh.Extensions.
  2. Add Thresh.Endpoints if repeated paths/DTOs justify typed endpoint groups.
  3. Add Thresh.Hosting and Thresh.HealthChecks for long-running service environments.
  4. Add Thresh.Reactive only if your team already operates with reactive pipelines.