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.
Read the analysisDistributed systems · FAANG-scale engineering
Production wisdom for engineers building at planetary scale.
exashard is a publication on distributed systems, Kubernetes, and the architecture that takes software from one million to one billion users — written from the trenches of running a real polyglot platform, not paraphrased from documentation.
Latest writing
All articles
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
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.
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.
Explore by discipline
Distributed Systems
Consensus, replication, and failure at scale
BrowseKubernetes
Operating clusters that do not page you at 3am
BrowseMicroservices
Polyglot services that compose, not collapse
BrowseSystem Design
Capacity math and tradeoffs that hold up
BrowseEngineering Strategy
The decisions above the code
BrowseNewsletter
The exashard dispatch
Production wisdom on distributed systems, delivered when there is something worth saying. No spam, unsubscribe anytime.