
The iOS Developer Who Picked Nomad Over Kubernetes for Yext's 2,000 Services
Tom Elliott joined Yext in 2015 as an iOS developer. Within a year, both his mobile projects were canceled.
Tom Elliott joined Yext in 2015 as an iOS developer. Within a year, both his mobile projects were canceled.
Just 2 years into his first “real” engineering job, Andy was running the engineering team. And a RethinkDB was a ticking time bomb.
In 2011, PagerDuty was using MySQL as a queue. If you just winced, you understand the problem.
"This is the most atypical job I’ve ever had—and I worked at WeWork."
Slack didn’t go down—but it came close, twice in a single day. Every service needed to be out of that AWS AZ.
Slack didn’t plan this migration in advance. It started because IBM was breaking the system.
You’d think migrations would be repeatable. But even the same teams, doing the same upgrade, don't always do the same work.
Slack’s memcached mostly worked — until it didn’t. Glen Sanford turned it from brittle and unowned to one of Slack’s most stable systems.
What does it take to migrate 150 services to Python 3? At Lyft, the answer wasn’t just automation.
Mike, a cybersecurity lawyer, works with companies after the worst has happened—ransomware, exfiltration, and worse.
Datadog’s observability platform was expanding rapidly, and they needed a new foundation. Enter Husky, their new columnar store, and a 3-year migration.
When Postgres 11 approached end-of-life, Ninad stepped in to upgrade a site with multiple Rails apps, multiple DB instances, and no in-house infra team.
If you were writing frontend code in 2013, you probably used CoffeeScript too. Hal Anil describe's Braze's journey to React and Typescript.
A deep dive on Matt Ouille's service catalog migration at scale
Ryan and I met at Slack. All we did was migrations.
Get the latest migration stories, right in your inbox.