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 the technical director for operations and reliability at the Financial Times. Her teams build operational and developer tooling and help engineering teams at the FT to support the systems they build, including coordination, communication and learning around major incidents. Previously, Sarah was a developer and tech lead for nearly 20 years. Building a new microservices-based system about five years ago led her to develop a deep interest in operability, observability, and DevOps—and learn a lot about containerization, Kubernetes, and Go in the process.
©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