Get the latest tech news

We run migrations across 2,800 microservices

’ve got a lot of value from our microservices architecture (2,800 and counting!), but this architecture is not without its challenges. One of those challenges is how to make sweeping library changes across all those services.

It’s worth classifying the required changes into these two categories up front to avoid nasty surprises and make it easier to track progress. There were some types/functions that were significantly different in the new library - it would require a lot of effort to update all call sites, and in some cases the benefit of the new API was minimal. This is why we have a strong bias towards centrally driven migrations; while one team must pay a relatively high price, we spend less effort overall and it significantly increases the chances that we retain consistency.

Get the Android app