Push notification
Typically, the communication between an API consumer and the API originates from the former and occurs in one direction. In this approach, when the most recent data (for example, changes made to a record) is required, it is the API consumer's responsibility to poll for changes (meaning constantly calling an API). Not only does this result in chatty interactions, but it is also highly inefficient from a transport use perspective. It can also result in poor user experience (for example, users having to refresh application screens so that data updates).
An approach to get around such limitations is to adopt a capability that enables bi-directional communication, such that the API itself can initiate a request to the API consumer(s). ...
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