Horizon vs Pusher: What are the differences?
Horizon and Pusher can be primarily classified as "Realtime Backend / API" tools.
Horizon is an open source tool with 6.77K GitHub stars and 389 GitHub forks. Here's a link to Horizon's open source repository on GitHub.
What is Horizon?
What is Pusher?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Horizon?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Horizon?
What are the cons of using Pusher?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
In the original prototype all the communication was handled by a backend server. Each client connected directly to the server using the socket.io library. This quickly proved to be messy and unreliable, especially on the cheap server being used to host it.
Websockets proved to be a little more reliable, but still just as messy and not all browsers support them. That's when the project was switched over to use Pusher. Using Pusher has allowed all but the initial connection code to be off-loaded onto the client. Now instead of communicating through a self-hosted server, clients can communicate pretty much peer-to-peer over Pusher.
Pusher is used to send update notification whenever Lapzbot joins a server.