As well as a WebSockets API, they have a HTTP API for publishing your messages. This is ideally suited to web server technologies and they have a set of HTTP API libraries in many common languages to help you to do this.
They also have a Publish/Subscribe model that allows developers to filter and control how messages are received.
You can use Pusher to create live activity streams (have feeds update in real times), live data visualizations (choropleth maps that stream new data continuously), live chats, etc!
Pusher API Libraries
Citing Pusher, “Sending and receiving messages using the Pusher API requires libraries. In this section you’ll find libraries for a variety of platforms:
Pusher libraries are divided into 2 categories:
- CLIENT libraries predominantly consume messages using a WebSocket interface. Think of them as subscribers, although it’s possible to publish messages using Client Events.
- SERVER libraries publish messages, request information using our HTTP API, authenticate channel subscriptions, and handle Webhook calls. Think of them as publishers, although it’s possible to subscribe to messages using Client Event Webhooks.”