Systems

Architecture notes, high-level design, and documented trade-offs.

Migration

Strangler Pattern

Migrate a monolith to microservices by shifting traffic gradually — so you can roll back without taking production down.

Mar 5, 2026

Migration

Distributed Monolith

Tight coupling over the network — distribution’s latency without microservice independence.

Jul 16, 2026

Migration

Microservice Independence

Loose coupling, independent deploy, low chatter, and independent scale — the checks before you split.

Jul 16, 2026

Data Management

CQRS

Separate reads from writes so combined views don’t fan out across every service database.

Feb 11, 2026

Data Management

Database per Service

Why each microservice should own its database — and what you give up when every service still shares one.

Mar 5, 2026

Data Management

Saga Pattern

Multi-service consistency via local transactions — and compensating actions when a step fails.

Mar 5, 2026

Coordination

Choreography vs Orchestration

Two ways to run a saga — peer services reacting to events, or a central orchestrator directing each step.

Mar 5, 2026

Coordination

Idempotency

Safe retries for POST — HTTP method basics, duplicate requests, idempotency keys, and handling them across servers.

Apr 19, 2026

Interview Foundations

Design a Scalable Web Application

The vaguest interview prompt is a test of structure — what to ask before you draw boxes.

Dec 10, 2025

Interview Foundations

Bounded Context

Same word, different meaning behind different walls — group events, stay independent, map to services.

Jul 16, 2026

Interview Foundations

Event Storming

Whiteboard the domain — list events, sequence them, find gaps, then group into contexts.

Jul 16, 2026

Interview Foundations

How Many Microservices

No magic number — derive services from domains and subdomains, not a target count.

Jul 16, 2026