Microservices
Modular Monolith vs Microservices: How to Choose
Modular monolith vs microservices: start with a modular monolith and extract services only when a real force demands it. The decision framework and the signals.
#architecture
9 articles
Microservices
Shared Libraries in Microservices: The Real Cost
Shared libraries in microservices promise reuse but quietly recouple services through a versioned dependency. When they help, when they hurt, and the rules.
Microservices
Breaking Service Dependency Cycles
Service dependency cycles make microservices impossible to deploy, test, or reason about in isolation. How to detect them and four ways to break them.
System Design
System Design Interviews for Senior Engineers
System design interviews for senior engineers reward judgment, not memorized diagrams. The framework, the tradeoff signals interviewers grade, and the traps.
Microservices
Bounded Contexts in Real Microservice Systems
Bounded contexts are how you find real microservice boundaries: split where the same word means different things. The practical guide, not the DDD theory.
Microservices
Service Ownership Boundaries in Microservices
Service ownership boundaries decide whether microservices scale your org or stall it. Draw them by data ownership and team, not by code size. The rules.
Microservices
Why Language Boundaries Break Polyglot Microservices
Polyglot microservices break at the seams, not inside services. The 5 cross-language failure modes (deadlines, cancellation, errors, types, connections) and fixes.
Microservices
FastAPI Microservices Architecture: A Production Guide
FastAPI microservices done right: where they belong in a polyglot fleet, the async model that decides performance, and the worker math most teams skip.
Distributed Systems
Go vs Rust for Microservices: When to Choose Which
Go vs Rust for microservices: use Go by default, reach for Rust only on hot paths where tail latency or memory is a measured need. The decision framework.