Please log in to watch this conference skillscast.
If you only have to do things a few times, you can do them manually. With microservices, you need to automate pretty much everything. Doing it manually just takes too long. And it’s not just provisioning and deployment pipelines. How do you keep service run books up to date for 100+ services? And how do you avoid being woken up overnight multiple times a week when you’re running millions of checks a day? In a distributed system, "grey failures" happen all the time. Finally, what about breaking API changes or decommissioning for a service you use everywhere? How do you avoid weeks of migration work every time? Sarah Wells explains why, when you have 100+ services, everything needs to be automated and shares tips and lessons learned from building and running a microservices-based system from scratch, including migrating the whole thing from microservices to containers and from fleet to kubernetes.
YOU MAY ALSO LIKE:
Keynote: Operating Microservices: Everything Is at Scale
I've been a developer for 15 years, leading delivery teams across consultancy, financial services and media. Over the last few years I have developed a deep interest in operability, observability and devops, and at the beginning of 2018, this led to me taking over responsibility for Operations and Reliability at the Financial Times.