Push and real-time communication based on HTTP, WebSocket Protocol

Use case about real-time and one-to-many communication like chat application, use Push Model with

HTTP and WebSocket Protocols.

▪ Build real-time two-way communication applications, such as chat apps and streaming dashboards like

the score of a sports game, with WebSocket APIs.

▪ The client and the server can both send messages to each other at any time. Backend servers can easily

push data to connected users and devices.

▪ Pull communication based on HTTP and AMQP (short polling - long polling)

Also called "Polling" and it's basically the same as refreshing your mail inbox every 5 minutes to check for

new mail. It is a call and ask model.

▪ This model is become a waste of bandwidth if there are no new messages and responses comes from the

server.

▪ Opening and closing connections is expensive. And we can say that this model doesn't scale well.

▪ Typically have limits like on Twitter on how often they allow you to call their API.

https://www.simplilearn.com/interactive-vs-push-vs-pull-communication-in-project-management-article