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 deployment pipelines. How do you keep service run books up to date for 100+ services or avoid being woken up overnight multiple times a week when you’re running millions of checks a day? Networks go wrong all the 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.
Sarah Wells is technical director for operations and reliability at the Financial Times. A developer with 15 years of experience, Sarah has led delivery teams across consultancy, financial services, and media. Over the last few years, she has developed a deep interest in operability, observability, and DevOps. Previously, she led work on FT’s semantic publishing platform, which makes it easy to discover and access all the FT’s published content via APIs in a common and flexible format. That project focused on Go, microservices, containerization, Kubernetes, and how to influence teams to do the right things.
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org