A RESTful approach to microservices can improve the stability and resilience of services, reduce the need for extensive changes and redeployment when the domain model changes, and greatly increase the flexibility of individual services, including the ability to automatically work with other newly discovered services. Mike Amundsen walks you through building adaptable microservices that take advantage of the features of REST, including statelessness, self-description, and using hypermedia to discover and modify application state. You’ll learn how to design services that advertise themselves to the network, discover their own “partner” services, and can adapt to subtle changes to existing services without relying only on recode-and-redeploy patterns for maintaining overall system operation.
What are RESTful microservices?
Models, messages, and vocabularies
Three types of microservices
Six stability patterns
Runtime service infrastructure
An adaptable system
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. • firstname.lastname@example.org