The Go programming language — idioms, patterns, and production usage.
OpenAI and Anthropic both document outages, overload codes, and best-effort availability. The survival kit: LLM-aware circuit breakers, same-model-first fallback chains, and degraded modes designed before you need them.
One agent, one context window, one serial loop — until it stalls at 40 minutes and 180K tokens. The orchestrator pattern fans work out to isolated sub-agents in parallel, then synthesizes. Here's the backend, in compiling Go.
Go 1.26 makes the Green Tea garbage collector the default. What actually changed, how to measure GC CPU before and after on your own workload, and the short window you have to opt out.
Go context.Context: constructors, cancellation, deadlines, request values, and five goroutine leak patterns in production.
2,500 API endpoints in one MCP server without blowing context windows. The Code Mode pattern uses search + execute to cut token cost by 1,000x.
Adding one cache server shouldn't invalidate every key. Consistent hashing with virtual nodes and bounded loads — full Go and Java implementations.
Probabilistic drop rate limiting: uncoordinated enforcement bypassing Redis for 1M+ RPS with zero coordination overhead.
Handle unpredictable JSON in Go: map[string]any, json.RawMessage, type switches, and defensive patterns for shifting schemas.
Go graceful shutdown: SIGTERM handling, health probe coordination, and Kubernetes drain patterns for zero dropped requests.
Why exactly-once is a myth, and how idempotency keys, database constraints, and the outbox pattern make retries safe in Go and Java.