Microservices is a popular but vague term. Definitions of microservices can vary depending on what you want them to accomplish and how you want them to communicate with each other.
Join Mike Amundsen to learn about the three types of microservices, see what makes them unique, and discover when you deploy each of them. Mike explains the difference between stateless, data-centric, and aggregator microservice models, how to identify which one you need to build, and the challenges to keeping each of them up and running in a complex distributed system. You’ll also learn how to apply Michael Nygard’s stability patterns (from his book Release It!) to ensure your microservice components are stable and resilient throughout the software life cycle, even when parts of your ecosystem fail.
Whether you are new to microservices or a veteran software developer or enterprise architect, you’ll get a better handle on how to design and build successful microservice components for your organization.
An internationally known author and speaker, Mike Amundsen travels the world consulting and talking about network architecture, Web development, and intersection of technology and society. He works with companies large and small to help them capitalize on the opportunities APIs and Microservices present for both consumers and the enterprise.
Amundsen has authored numerous books and papers. He contributed to the O’Reilly Media book, “Continuous API Management” (2018). His “RESTful Web Clients”, was published by O’Reilly in February 2017 and he co-authored “Microservice Architecture” (June 2016). Amundsen’s 2013 collaboration with Leonard Richardson “RESTful Web APIs” and his 2011 book, “Building Hypermedia APIs with HTML5 and Node”, are common references for building adaptable Web applications. His latest book “Design and Build Great APIs” for Pragmatic Publishing is scheduled for release in early 2019.
©2018, O’Reilly UK Ltd • (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