What do you think?
Rate this book
RESTful Web API Patterns and Practices Cookbook: Connecting and Orchestrating Microservices and Distributed Data
Many organizations today orchestrate and maintain apps that rely on other people's services. Software designers, developers, and architects in those companies often work to coordinate and maintain apps based on existing microservices, including third-party services that run outside their ecosystem. This cookbook provides proven recipes to help you get those many disparate parts to work together in your network.
Author Mike Amundsen provides step-by-step solutions for finding, connecting, and maintaining applications designed and built by people outside the organization. Whether you're working on human-centric mobile apps or creating high-powered machine-to-machine solutions, this guide shows you the rules, routines, commands, and protocols--the glue--that integrates individual microservices so they can function together in a safe, scalable, and reliable way.
Design and build individual microservices that can successfully interact on the open webIncrease interoperability by designing services that share a common understandingBuild client applications that can adapt to evolving services without breakingCreate resilient and reliable microservices that support peer-to-peer interactions on the webUse web-based service registries to support runtime "find-and-bind" operations that manage external dependencies in real timeImplement stable workflows to accomplish complex, multiservice tasks consistently
Author Mike Amundsen provides step-by-step solutions for finding, connecting, and maintaining applications designed and built by people outside the organization. Whether you're working on human-centric mobile apps or creating high-powered machine-to-machine solutions, this guide shows you the rules, routines, commands, and protocols--the glue--that integrates individual microservices so they can function together in a safe, scalable, and reliable way.
Design and build individual microservices that can successfully interact on the open webIncrease interoperability by designing services that share a common understandingBuild client applications that can adapt to evolving services without breakingCreate resilient and reliable microservices that support peer-to-peer interactions on the webUse web-based service registries to support runtime "find-and-bind" operations that manage external dependencies in real timeImplement stable workflows to accomplish complex, multiservice tasks consistently
719 pages, Kindle Edition
Published October 17, 2022
10 people are currently reading
63 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
May 7, 2025
Disconnected from reality, buzzwords, smoke, rote learning.
Contains zero useful information for both the architect and the developer, it is just a long list of definitions, citations and historical anecdotes. A fair name for the book would have been "Restful APIs: history and definitions".
Pushes for the concept of hypermedia which is only valid for a tiny amount of API real life scenarios and it's mostly harmful because it introduces unnecessary overheard due to extra serialization and deserialization and extra network usage. The advices of this book will only add clutter to applications and networks.
It is based on the assumption that APIs are "likely to be used in unexpected ways by unknown people" while in my experience this is never the case. I have 10 years of experience in the industry in multiple companies and sectors: the APIs I dealt with were used in precisely defined way by a list of know clients.
Contains zero useful information for both the architect and the developer, it is just a long list of definitions, citations and historical anecdotes. A fair name for the book would have been "Restful APIs: history and definitions".
Pushes for the concept of hypermedia which is only valid for a tiny amount of API real life scenarios and it's mostly harmful because it introduces unnecessary overheard due to extra serialization and deserialization and extra network usage. The advices of this book will only add clutter to applications and networks.
It is based on the assumption that APIs are "likely to be used in unexpected ways by unknown people" while in my experience this is never the case. I have 10 years of experience in the industry in multiple companies and sectors: the APIs I dealt with were used in precisely defined way by a list of know clients.
Displaying 1 of 1 review