Microservices are an increasingly popular approach to building cloud-native applications, and dozens of new technologies that streamline adopting microservices development, such as Docker, Kubernetes, and Envoy, have been released over the past few years. Phil Lombardi, Rafael Schloming, and Richard Li walk you through actually using these technologies to develop, deploy, and run microservices. Along the way, they discuss the evolution of the microservices stack, key things to keep in mind when adopting microservices, and how to tune and evolve your microservices architecture.
Essentials: Development and deployment
Resilience and monitoring
Adapting these techniques to your organization
Phil Lombardi is a senior platform engineer at Datawire, where he is building the cloud services for Datawire.io’s resilient microservices framework. Phil has extensive experience building and operating distributed systems and continuous delivery pipelines in both the internet of things and web services spaces.
Rafael Schloming is the CTO of Datawire. Rafael is a coauthor of the Advanced Message Queuing Protocol (AMQP) specification and the primary architect of the open source Apache Qpid Proton project. Previously, he was a principal software engineer at Red Hat, where he worked on messaging technologies.
Richard Li is cofounder and CEO of Datawire. Datawire supports several popular open source tools for Kubernetes, including Telepresence (a local development on Kubernetes) and the Ambassador API Gateway. Richard is a veteran of multiple technology startups including Duo Security, Rapid7, and Red Hat. He is a recognized Kubernetes and microservices expert and has spoken at numerous conferences including ApacheCon, the Microservices Practitioner Summit, and O’Reilly Velocity. He holds both a BS and MEng in computer science from MIT.
©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