“"Make the right engineering choice the easy one." — Wise platform engineering philosophy (source: ByteByteGo article citing Wise Engineering Blog, verified 2026-05-04)”
You know that feeling when your 50th microservice has slightly different logging than your 1st, your 30th service has a custom authentication setup three versions behind, and your security team can't audit any of it because nothing is consistent? At 850 engineers and 1,000+ services, Wise faced exactly this: how do you stop every team from independently reinventing security middleware, observability config, and database connection setup — and then diverging from each other over 18 months? The naive answer is documentation and code reviews. The real answer is making the standard the only dependency in the build file.
Wise's backend runs 1,000+ Java/Kotlin microservices, all consuming a single versioned Gradle artifact called the Microservice Chassis. Think of it like a standard electrical socket: every appliance (service) plugs in and immediately gets power, grounding, and surge protection (security, observability, DB connections, Kafka) — no team configures these from scratch. When Wise's platform team bumps the chassis version, all 1,000+ services inherit the change at their next build. Deployments flow through GitHub Actions CI into Spinnaker, which routes 5% of real traffic to the new version for a 30-minute observation window before full rollout — with automatic rollback if anomalies appear. The entire observability layer (Loki for logs, Grafana for dashboards, Tempo for traces, Mimir for metrics) runs on dedicated isolated clusters, ingesting 6 million metric samples per second without competing for production compute.
If you are a platform engineer, backend architect, or engineering manager at a company with 50+ engineers and more than 20 microservices, this stack gives you a concrete reference point for platform standardization. The Microservice Chassis pattern is especially relevant if your services are visibly diverging on security and observability config. Not useful if you are pre-product-market-fit or running fewer than 10 services — the platform team investment required to maintain a shared versioned artifact is only justified when service count pushes coordination overhead past what code reviews ca...
Yes, if you are designing a platform engineering strategy for a 50+ engineer org. The Microservice Chassis pattern, LGTM observability stack, and Spinnaker canary approach are all either open-source or reproducible with open-source tooling. The caveat: every number in this article is self-reported by Wise's engineering team with no independent verification — the original Wise Engineering Blog post received 1 HN point and 0 comments, so none of these claims have been publicly challenged or corroborated.
Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.