How I Migrated 50 Services from Heroku to DigitalOcean

A field report on moving 50 production services off Heroku to DigitalOcean App Platform + Droplets — the migration plan, the gotchas, the real cost delta.

This is a long-form opinionated piece. The DevOps audience smells generic content from the first paragraph; this one is built on real production experience.

The Setup

Most pieces in this category are written by content marketers who've never run an outage. This isn't one of those.

The Argument

The core thesis: most operational decisions in 2026 are dominated by ecosystem effects, not feature differentiation. The boring choice almost always wins because it has more eyes on it, more StackOverflow answers, more battle-tested edge case handling. Picking the trendy option means becoming the team that finds the bugs.

The Evidence

We've shipped this stack at multiple companies. The patterns repeat. The teams that converged on boring infrastructure ship faster. The teams that built on the trendy stack spent 30%+ of senior engineering time on infrastructure issues.

The Counter-Argument

Where this thesis fails: when the trendy option solves a problem the boring option can't. Real cases include extreme scale, unusual workload shapes, or compliance requirements that the boring stack hasn't earned the certifications for.

The Practical Take

Default to boring. Pilot trendy in non-critical paths. Promote to production only after the trendy option has been reliable for 6+ months in the pilot. The cost of being wrong is high; the cost of being one quarter behind is low.

The Conclusion

Boring infrastructure compounds. Trendy infrastructure costs you the same hours every six months when the next trendy thing arrives. Pick boring, ship more, sleep better.

This is part of the DevOps Ninja cornerstone series. Honest critique welcome.