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 speaker, Mike Amundsen travels the world consulting and talking about network architecture, web development, and the 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. Mike 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 coauthored Microservice Architecture (June 2016). His 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. • firstname.lastname@example.org