When you’re operating multiple services, outages can feel like murder mysteries. Building out forensics tools such as monitoring and observability is essential. Unfortunately, it’s a real challenge to balance priorities between building new features and tools to help pinpoint root causes.
Linkerd 2.0 provides many of the tools you need to tame the chaos of operating microservices in a cloud native world. Because it’s a transparent proxy that runs alongside your application, there are no code changes required. It even comes with Prometheus to store the metrics for you and prebuilt Grafana dashboards to show exactly what’s important for your services—success rate, latency, and throughput.
Thomas Rampelberg explains the benefits Linkerd offers, demos the installation of Linkerd on Kubernetes, and debugs a real-world problem. He digs into what functionality you can build on top of the tools provided by Linkerd, such as alerting and autoscaling. By the end he’ll have answered the following questions: What is a service mesh? How does a service mesh work? Why does my code not change? Who benefits from these tools? When do I need to add Linkerd to my services?
Code samples and resources will be provided.
Thomas Rampelberg is a software engineer at Buoyant. He’s made a career of building infrastructure software that allows developers and operators to focus on what’s important to them. Previously at Mesosphere, he helped create DC/OS, one of the first container orchestration platforms used by many of the Fortune 500. He has moved to the next big problem in the space: providing insight into what’s happening between services, improving reliability between them, and using best practices to secure the communication channels between them.
©2019, 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. • email@example.com