Container deployment platforms are a boring part of our infrastructure. The exciting parts, unfortunately, happen when services actually try communicating and working together to accomplish some business function. The service mesh approach helps make service communication boring, with capabilities that include retries, load balancing, timeouts, deadlines, circuit breaking, mutual TLS, service discovery, and distributed tracing. Istio—an open source project initially sponsored by Google, Lyft, and IBM—has become a popular way of implementing a service mesh, and the project has a growing community of users and contributors.
Christian Posta leads a deep dive into Istio. You’ll learn how Istio works and how to debug issues as you take a step-by-step walk-though of Istio’s components. Christian starts by introducing Envoy, Istio’s default service proxy, teaching you how to configure it and how it implements resilience functionality. You’ll then deploy each component of the Istio control plane—Istio Pilot, Istio Ingress, Istio Gateway, and Istio Mixer—giving you a firm understanding of what they do and how to use them. You’ll also discover how to debug Envoy configurations and how best to replace resilience features handled by library-specific frameworks (Netflix OSS, Finagle, etc.).
Christian Posta is chief architect for cloud applications at Red Hat. Christian has spent a great deal of time working with large companies creating and deploying large-scale distributed architectures—many of which are now called microservices based. A frequent blogger, speaker, and open source enthusiast, Christian is the author of Microservices by Example and a committer on the open source projects Apache ActiveMQ, Apache Camel, Fabric8.io, and others. Christian enjoys mentoring, training, and leading teams to be successful with distributed systems concepts, microservices, DevOps, and cloud-native application design.
©2018, 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