API aggregator
Problem statement:
A consuming application (for example, a mobile or JavaScript browser app) has little choice but to make multiple calls to different APIs in support of a single user journey. Take, for example, an eCommerce mobile app. When a user opens the app and the main page loads, typically a summary of the customer details, the latest orders placed, and even the loyalty status level and points are displayed all on the same page. However, the information displayed won't come from the same source and thus multiple APIs have to be called in order to collect all the information required and subsequently present it in the desired format.
This approach can result in inefficiencies, such as increased complexity in the client-side ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access