Skip to content
All topics

System Design

Architecture styles from monolith to cell-based, sized small to enterprise, with HLDs, LLDs and trade-offs.

17 long reads · 216 minutes in total

  1. System Design Interview Questions: Multi-Tenant Isolation and Noisy Neighbors

    Practice 12 system design interview questions on tenant isolation, fair resource sharing, and the trade-offs behind multi-tenant platforms.

    20 Nov 202614 min

  2. Serverless Architecture Blueprint: When Functions Beat Containers

    A medium-scale AWS blueprint for deciding when event-driven functions simplify delivery, with concrete data, deployment, resilience, observability, and cost guidance.

    13 Nov 202618 min

  3. System Design Interview Questions: Overload Control and Graceful Degradation

    Thirteen system design interview questions on keeping services useful under load, handling dependency failures, and recovering safely.

    8 Nov 202615 min

  4. Bounded Contexts First: A Modular Monolith That Can Become Services

    An AWS blueprint for a modular monolith with enforceable context boundaries, reliable events, context-owned data, and a practical extraction path that does not require an early microservices tax.

    2 Nov 202617 min

  5. The well-built monolith: a layered architecture blueprint for a startup MVP

    30 Oct 20268 min

  6. Consistency Models: Spend Latency Only Where Correctness Needs It

    Choose consistency per operation, preserve the guarantees users rely on, and use replication lag and latency measurements to tune the rest.

    30 Oct 20269 min

  7. CAP Theorem: What a Network Partition Forces You to Choose

    CAP is not a menu of two guarantees to select in advance; it explains why a partition forces replicated systems to trade off linearizable consistency against availability.

    29 Oct 20269 min

  8. Choosing Where Capacity Goes: Horizontal and Vertical Scaling

    Vertical scaling gives one machine more capacity; horizontal scaling spreads work across machines. The right choice depends on bottlenecks, state, failure tolerance, and operational cost.

    28 Oct 20268 min

  9. Load Balancing Traffic Steering: A Control Plane and Data Plane Design

    Design traffic steering as a versioned control plane that publishes safe routing policy to fast, independent data planes, with explicit health, locality, capacity, and failure behavior.

    27 Oct 202611 min

  10. Cache Invalidation Is a Consistency Protocol, Not a Delete Call

    Cache invalidation is difficult because writes, readers, and cache failures race; choose an explicit freshness contract and design invalidation around it.

    26 Oct 20269 min

  11. C# Interview Guide: SQL Server Transaction Isolation Levels — RCSI vs SNAPSHOT

    Q16 — Transaction Isolation Levels — READ COMMITTED SNAPSHOT vs SNAPSHOT Level: Senior | Topic: SQL Server Why Isolation Levels Matter Isolation levels control how transactions see data changed by concurrent transactions...

    5 Jun 202612 min

  12. 10 .NET Production Features — Architecture Map

    Here's a comprehensive breakdown of all 10 features, from junior through to principal engineer level. I'll build a visual architecture overview first, then walk through each. Now let's go deep on each feature, level by l...

    17 May 202612 min

  13. 15 Must-Know Design Patterns Every Software Engineer and Architect Should Understand

    Design patterns are reusable solutions to common software design problems. They are not copy-paste code templates, but proven architectural ideas that help teams build systems that are easier to extend, test, maintain, a...

    15 May 202627 min

  14. All Major Architectures in .NET Core

    1. Monolithic Architecture Extracted description: A single codebase and single deployable unit where all components are tightly coupled. Structure: UI / Web API → Business Logic + Data Access + Shared Components → Databa...

    13 May 202615 min

  15. Sagas & Long‑Running Workflows: Patterns for Distributed Transactions

    Sagas provide a pragmatic way to manage multi‑service transactions using local transactions plus compensations. This article compares choreography and orchestration and gives examples.

    11 May 202612 min

  16. Event Sourcing: Design Patterns, Pitfalls, and Rebuild Strategies

    Event sourcing records every change as an immutable event. This article explains modeling choices, snapshots, upcasters, and safe external integrations.

    11 May 20268 min

  17. CQRS in Production: Patterns, Trade‑offs, and Practical Recipes

    A practical, example-driven guide to applying CQRS in real systems: when to use it, how to handle eventual consistency, the Outbox pattern, and operational considerations.

    11 May 202612 min

Newsletter

Get new System Design reads on Saturday.

The week’s new long reads on architecture, cloud and AI — with the diagrams left in. Delivered Saturday morning, no noise in between.

One email every Saturday. Unsubscribe with one click, any time.