Microservices

How retry budgets keep microservice retries useful without letting clients amplify overload, including per-request limits, client retry ratios, token buckets, retry metadata, and production metrics.

How correlation IDs in microservices connect logs, traces, queues, and background jobs across service boundaries without pretending to replace real tracing or metrics.

How to implement the transactional outbox pattern for reliable event publishing, including schema design, relay claiming, retries, duplicate handling, ordering, CDC, monitoring, and cleanup.

How to use rate limiting, backpressure, and load shedding to keep microservices inside safe capacity, with failure timelines, TypeScript admission controls, queue policies, rollout steps, and production metrics.

How the circuit breaker pattern protects microservices from cascading failures, including closed/open/half-open states, slow-call thresholds, fallback behavior, retry interaction, rollout checks, and production metrics.