Production-proven writing on distributed systems, Kubernetes, microservices, and scaling software from 1M to 1B+ users. Staff-engineer depth, no fluff.https://exashard.comenhttps://exashard.com/posts/grpc-across-languages-production-lessonshttps://exashard.com/posts/grpc-across-languages-production-lessonsgRPC across languages promises neutral RPC. In production the gaps are real: load balancing, deadlines, status codes, and schema evolution. The fixes.Thu, 25 Jun 2026 00:00:00 GMTDistributed Systemsgrpcprotobufmicroservicespolyglotdistributed-systemssupport@colsonsuperapps.com (Colson)https://exashard.com/posts/building-rust-hot-path-services-in-productionhttps://exashard.com/posts/building-rust-hot-path-services-in-productionRust hot path services hold their latency target only if you set 4 defaults right: panic strategy, allocator, Tokio runtime, and bounds. The production checklist.Wed, 24 Jun 2026 00:00:00 GMTDistributed Systemsrustmicroservicesperformancetokioproductionsupport@colsonsuperapps.com (Colson)https://exashard.com/posts/why-language-boundaries-break-polyglot-microserviceshttps://exashard.com/posts/why-language-boundaries-break-polyglot-microservicesPolyglot microservices break at the seams, not inside services. The 5 cross-language failure modes (deadlines, cancellation, errors, types, connections) and fixes.Tue, 23 Jun 2026 00:00:00 GMTMicroservicespolyglotmicroservicesgrpcdistributed-systemsarchitecturesupport@colsonsuperapps.com (Colson)https://exashard.com/posts/fastapi-microservices-architecture-a-production-guidehttps://exashard.com/posts/fastapi-microservices-architecture-a-production-guideFastAPI microservices done right: where they belong in a polyglot fleet, the async model that decides performance, and the worker math most teams skip.Mon, 22 Jun 2026 00:00:00 GMTMicroservicesfastapipythonmicroservicesasgiarchitecturesupport@colsonsuperapps.com (Colson)https://exashard.com/posts/go-vs-rust-for-microservices-when-to-choose-whichhttps://exashard.com/posts/go-vs-rust-for-microservices-when-to-choose-whichGo 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.Sun, 21 Jun 2026 00:00:00 GMTDistributed Systemsgorustmicroservicesarchitectureperformancesupport@colsonsuperapps.com (Colson)