Pusher vs SignalR: What are the differences?
Pusher: Hosted APIs to build realtime apps with less code. Pusher is the category leader in delightful APIs for app developers building communication and collaboration features; SignalR: A new library for ASP.NET developers that makes developing real-time web functionality easy. SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization.
Pusher and SignalR can be categorized as "Realtime Backend / API" tools.
"An easy way to give customers realtime features" is the top reason why over 44 developers like Pusher, while over 7 developers mention "Supports .NET server" as the leading cause for choosing SignalR.
SignalR is an open source tool with 7.73K GitHub stars and 2.19K GitHub forks. Here's a link to SignalR's open source repository on GitHub.
According to the StackShare community, Pusher has a broader approval, being mentioned in 123 company stacks & 42 developers stacks; compared to SignalR, which is listed in 20 company stacks and 16 developer stacks.
What is Pusher?
What is SignalR?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
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.