Will Sewell
![Title image for "How we run migrations across 2,800 microservices"](https://images.ctfassets.net/ro61k101ee59/12wPdBj9XHeYmldaPvjFpr/f8887c9fdb78c3b5663319aeb66483dd/Preview_Link.png?w=2160&q=75)
How we run migrations across 2,800 microservices
We’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.
![](https://images.ctfassets.net/ro61k101ee59/4s4myNEBCsdZrP7lIGBnsA/c1b056542af37431abf760a84f28fc95/How_it_works.png?w=989&q=75)
Argo Rollouts at scale: Bringing Automated Rollbacks to 2,100+ services at Monzo
We introduced automated rollbacks to our platform using Argo Rollouts and made it the default deployment strategy for all our services. This helps us roll out changes safely and catch a wide class of problems related to deploying new code
![](https://images.ctfassets.net/ro61k101ee59/37Z7jbz9K59N9Yf9SfFy3G/677a277d7d8119af9b255b39dd700e25/9_Hero_Mobile.png?w=1524&q=75)
How we deploy to production over 100 times a day
Our success relies on us rapidly shipping new features. To achieve this rapid release cadence, we’ve optimised our engineering culture, tooling, and architecture to go from idea to production as frictionless as possible, without sacrificing safety.