HeartFlow-scale healthtech (pattern case) · 2021 · cost index 4/5
Big-bang microservices cutover weekend
Weekend cutover rollback; months of dual-run and incident debt
What happened
A clinical SaaS vendor with real revenue decided the monolith was "blocking scale." Leadership scheduled a flag-day migration to dozens of services, Kubernetes, and new data paths — because Netflix slides said that is what grown-ups do.
Failure mode
Strangler fig skipped in favor of a heroic cutover. Observability, idempotency, and backfill jobs were "phase two." Production traffic hit new services missing edge cases the monolith had absorbed for years. Rollback plans assumed the old system still existed unchanged — it did not.
Lesson
Microservices are a scaling strategy for organizations with SRE budgets and domain boundaries, not a weekend deploy pattern. If you cannot run old and new in parallel with measurable parity, you are not migrating — you are gambling with patient data and ARR.
Sources
- Industry postmortem pattern — flag-day microservice cutovers
- CNCF case studies — migration anti-patterns
- Charity Majors — observability before decomposition
Related tech
Architecture · 2012–now
Microservices Everywhere
Independent deployability as religion. Correct for some; ruinous cargo-cult for most.
$ Teams split 4-person products into 40 services, then hired SREs to babysit the mesh. Many later consolidated — after years of distributed tracing invoices and on-call trauma. See case studies on premature microservices and big-bang cutovers for named failure modes.
Platform · 2014–now
Kubernetes
Container orchestration that became the cloud's OS. Overkill for many; unavoidable for many others.
Platform · 2013–now
Docker / Containers
Ship the environment with the code. The packaging unit of modern compute.
Practice · 1995–now
Big-bang rewrite
Replace the working system instead of strangling it. A perennial money pit with new branding each decade.
$ "We'll freeze features and rewrite in the hot language." Multi-year projects shipped late, incomplete, or not at all — while competitors iterated on the ugly system that made money.
Architecture · 1970–now
Modular monolith
One deployable with clear boundaries. The unfashionable default that keeps shipping while microservices argue about ownership.
Architecture · 2015–now
gRPC
Binary RPC with contracts. Fast internal glue that should never face the public internet without a gateway.