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: Quality for 'Cloud Natives': What Changes When Your Systems Are Complex And Distributed? (SkillsCast recorded in September 2019)
• FullStack Event Sourcing and Applied DDD with Roman Sachse (Online Course on 23rd - 25th September 2020)
• Domain Models in Practice: DDD, CQRS & Event Sourcing with Marco Heimeshoff (Online Course on 28th September - 2nd October 2020)
• Building and Leading Remote Teams (Online Meetup on 19th August 2020)
• Building a Cloud Native Application with Quarkus (Online Meetup on 27th August 2020)
• Debugging Containers on Kubernetes with "kubectl debug" (SkillsCast recorded in July 2020)
• Applied Domain-Driven Design — Full-Stack Event Sourcing (SkillsCast recorded in July 2020)