Production patterns

This page captures practical guidance for stable long-running deployments.

Recommended defaults

• Keep retries conservative.
• Keep circuit breaker thresholds realistic for your workload.
• Use explicit cancellation in all outward-facing operations.

Runtime patterns

• Treat reconnect as normal, not exceptional.
• Keep event handlers fast; offload heavy work.
• Separate transport DTOs from business models.

Operational guardrails

• Emit structured logs with correlation IDs where available.
• Track latency and failure budgets.
• Add alerts for reconnect storms and sustained HTTP failures.

API stability note

Core abstractions (ILcuHttpClient, IEventStream) are the primary stability boundary. Typed endpoint groups are convenience layers and can evolve with LCU endpoint realities.