Composing IChatClient Middleware: Why Order Matters
Compare cache, retry, and telemetry order around IChatClient with a fake provider, exact event traces, cancellation, and a streaming failure.
Compare cache, retry, and telemetry order around IChatClient with a fake provider, exact event traces, cancellation, and a streaming failure.
Use admission control, bounded waiting, and shared provider limits to keep slow AI work from turning overload into an outage, with C# examples.
Qualify fallback models against the feature contract, define eligible failures, bound attempts, and make reduced behavior visible to callers.
Compose shared chat-client behavior in .NET without moving feature policy into middleware or hiding streaming, caching, and retry costs.
How to keep an AI-enabled product useful when a dependency fails, without hiding reduced capability or returning unsafe substitutes.
A small ASP.NET Core foundation for model access, validated configuration, tracing, buffered and streaming HTTP contracts, and future AI capabilities.
List a feature’s required model capabilities and check them in one request flow before comparing candidate deployments.
Register .NET AI clients, tools, prompts, and retrieval services with explicit lifetimes, safe request state, and clear disposal ownership.
Design human approval around an exact operation, with reviewable payloads, durable decisions, expiry, and execution checks that survive retries.
How to bound time, tokens, retries, tool calls, and estimated cost across a complete AI execution instead of limiting each call in isolation.