The Technology Migrations series
The Technology Migrations series
Migrations are a messy business. They always run far behind schedule, and it is actually quite rare for them to end at all. They are hard to justify in terms of return on investment. They have a bad reputation among both users and management. They are emotionally draining. Yet they are the way things move forward, technologically speaking at least.
Having been working for my entire career (so far) on internal teams focused on infrastructure or platforms, I end up thinking about migrations a lot. I have built my own little taxonomy of technology migrations, I have come up with my personal recipe to pull them off, and I have initiated engineers in the craft of running them. And those are the topics and the intent of this series of blog posts.
The first post goes over the taxonomy of migrations and how to approach them based on the category they belong to. But you can start from the second one if you are only interested in how to run the most common type. In case you have read the entire thing already or you don’t have time for long reads, you can find a summary checklist to follow during your migration in the very last post.
- A taxonomy of migrations
- Migrations under monopoly: Preparations
- Migrations under monopoly: Alpha
- Migrations under monopoly: Beta
- Migrations under monopoly: Automation
- Migrations under monopoly: Nudges
- Migrations under monopoly: The fat tail
- Migrations under monopoly: Deprecation
- The migration checklist
Antonio Uccio Verardi
from meta import engineering_manager