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.
Guide · 6-part series
Polyglot Microservices: Choosing the Right Language
A connected series on language selection for microservices: the decision frameworks, the production defaults that actually matter, and the cross-language failure modes nobody warns you about. Read in order, or jump to the decision you are facing.
-
- 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.
- 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.
- Distributed Systems
Building Rust Hot Path Services in Production
Rust hot path services hold their latency target only if you set 4 defaults right: panic strategy, allocator, Tokio runtime, and bounds. The production checklist.
- Distributed Systems
gRPC Across Languages: Production Lessons
gRPC across languages promises neutral RPC. In production the gaps are real: load balancing, deadlines, status codes, and schema evolution. The fixes.
- Distributed Systems
Protobuf Schema Evolution Without Breaking Clients
Protobuf schema evolution has clear rules: keep field numbers stable, reserve removals, add not mutate. The safe-vs-breaking change cheat sheet and why.
