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 lecturer, Mike Amundsen travels the world consulting and speaking on a wide range of topics, including distributed network architecture, web application development, and other subjects. Mike is the director of architecture for the API Academy, where he heads up the API architecture and design practice in North America and is responsible for working with companies to provide insight on how to best capitalize on the myriad opportunities APIs present to both consumers and the enterprises themselves. Mike has authored numerous books and papers on programming over the last 15 years, including RESTful Web APIs, a collaboration with Leonard Richardson, and Building Hypermedia APIs with HTML5 and Node, an oft-cited reference on building adaptable web applications. His most recent book, RESTful Web Clients, was released in early 2017 by O’Reilly.
©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