Apollo vs SignalR: What are the differences?
Developers describe Apollo as "GraphQL server for Express, Connect, Hapi, Koa and more". Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes. On the other hand, SignalR is detailed as "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.
Apollo can be classified as a tool in the "Platform as a Service" category, while SignalR is grouped under "Realtime Backend / API".
"From the creators of Meteor" is the top reason why over 8 developers like Apollo, while over 7 developers mention "Supports .NET server" as the leading cause for choosing SignalR.
Apollo and SignalR are both open source tools. It seems that SignalR with 7.75K GitHub stars and 2.19K forks on GitHub has more adoption than Apollo with 7.53K GitHub stars and 935 GitHub forks.
CircleCI, Swat.io, and Flexport are some of the popular companies that use Apollo, whereas SignalR is used by simplement-e, Jet.com, and NRGSoft. Apollo has a broader approval, being mentioned in 131 company stacks & 127 developers stacks; compared to SignalR, which is listed in 22 company stacks and 18 developer stacks.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Apollo?
What is SignalR?
Need advice about which tool to choose?Ask the StackShare community!
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