https://bhuvnesharya.com Software architecture, system design, and AI engineering writing. en https://bhuvnesharya.com/writing/choosing-databases-workload-design https://bhuvnesharya.com/writing/choosing-databases-workload-design Sun, 18 Oct 2026 00:00:00 GMT Compare relational, document, key-value, and search stores using realistic workloads. Treat polyglot persistence as a cost, not a default. https://bhuvnesharya.com/writing/observability-in-distributed-systems https://bhuvnesharya.com/writing/observability-in-distributed-systems Thu, 15 Oct 2026 00:00:00 GMT Logs, metrics, and traces only help when correlation, SLIs, and alerts map to user-visible failure. Learn what to measure and which habits waste time. https://bhuvnesharya.com/writing/designing-for-failure https://bhuvnesharya.com/writing/designing-for-failure Tue, 13 Oct 2026 00:00:00 GMT Follow a request through timeouts, retry budgets, idempotency, circuit breakers, and bulkheads. See why naive retries can deepen an outage. https://bhuvnesharya.com/writing/sync-vs-async-communication https://bhuvnesharya.com/writing/sync-vs-async-communication Sun, 11 Oct 2026 00:00:00 GMT Request-response, queues, and event streams solve different coupling problems. An order-processing walkthrough shows when each earns its complexity. https://bhuvnesharya.com/writing/designing-microservices-with-ddd https://bhuvnesharya.com/writing/designing-microservices-with-ddd Thu, 08 Oct 2026 00:00:00 GMT Microservices fail when teams cut by nouns instead of by change. Domain-Driven Design gives a sharper knife: bounded contexts, language boundaries, and a clearer case for waiting. https://bhuvnesharya.com/writing/why-event-driven-architecture https://bhuvnesharya.com/writing/why-event-driven-architecture Mon, 05 Oct 2026 00:00:00 GMT Event-driven architecture is a response to specific coupling problems. Use it when independent consumers and temporal decoupling matter; skip it when you only needed a queue or a function call. https://bhuvnesharya.com/writing/architecture-tradeoffs-behind-technology-choices https://bhuvnesharya.com/writing/architecture-tradeoffs-behind-technology-choices Fri, 02 Oct 2026 00:00:00 GMT Every technology choice encodes trade-offs about latency, coupling, operability, and failure. Make those trade-offs explicit before the logo on the diagram becomes the decision. https://bhuvnesharya.com/writing/quality-attributes-shape-architecture https://bhuvnesharya.com/writing/quality-attributes-shape-architecture Mon, 28 Sep 2026 00:00:00 GMT Turn 'make it fast and reliable' into scenarios you can design and verify against, then watch how those scenarios force structural choices. https://bhuvnesharya.com/writing/system-design-vs-software-architecture https://bhuvnesharya.com/writing/system-design-vs-software-architecture Thu, 24 Sep 2026 00:00:00 GMT System design and software architecture are not rival camps. They are different zooms on the same system, and the boundary moves with context. https://bhuvnesharya.com/writing/approaching-system-design-why-what-before-how https://bhuvnesharya.com/writing/approaching-system-design-why-what-before-how Sun, 20 Sep 2026 00:00:00 GMT Before you pick Kafka, Kubernetes, or a fashionable service split, write down the outcome, the users, the load assumptions, and what must not fail.