architecture

Business rules that scatter across routers, schemas and models are a domain problem, not a FastAPI one. Here's how Evans' own layered architecture fixes it, one bounded context at a time.

The simplest event-driven design is never the finished one. This post builds an order fulfillment system one design change at a time, each one fixing a concrete failure the last couldn't, from a synchronous handler to a production-ready, choreographed architecture.

Why your HTTP endpoint shouldn't talk to Kafka directly, how a consumer fits inside FastAPI's event loop, and why Kubernetes pods don't remember what they just learned.