Need advice about which tool to choose?Ask the StackShare community!

SignalR

488
1.2K
+ 1
146
Supabase

326
332
+ 1
24
Add tool

SignalR vs Supabase: What are the differences?

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; Supabase: The open source Firebase alternative. Supabase is currently in early-Alpha .It is an open-source Firebase alternative. It adds realtime and RESTful APIs to your PostgreSQL database without a single line of code.

SignalR and Supabase can be primarily classified as "Realtime Backend / API" tools.

SignalR is an open source tool with 8.06K GitHub stars and 2.23K GitHub forks. Here's a link to SignalR's open source repository on GitHub.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of SignalR
Pros of Supabase
  • 32
    Supports .NET server
  • 25
    Real-time
  • 18
    Free
  • 16
    Fallback to SSE, forever frame, long polling
  • 15
    WebSockets
  • 10
    Simple
  • 9
    Open source
  • 8
    Ease of use
  • 8
    JSON
  • 5
    Cool
  • 0
    Azure
  • 6
    Relational Database
  • 5
    Self hosting
  • 3
    Free
  • 2
    Open source
  • 2
    Postgres hosting
  • 2
    Easy deployment
  • 1
    Focus on product, not on deployment
  • 1
    Faster development
  • 1
    Realtime
  • 1
    Huge time-saver

Sign up to add or upvote prosMake informed product decisions

Cons of SignalR
Cons of Supabase
  • 2
    Expertise hard to get
  • 2
    Requires jQuery
  • 1
    Weak iOS and Android support
  • 1
    Big differences between ASP.NET and Core versions
  • 0
    No cons

Sign up to add or upvote consMake informed product decisions

What is SignalR?

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.

What is Supabase?

Supabase is currently in early-Alpha .It is an open-source Firebase alternative. It adds realtime and RESTful APIs to your PostgreSQL database without a single line of code.

Need advice about which tool to choose?Ask the StackShare community!

What companies use SignalR?
What companies use Supabase?
See which teams inside your own company are using SignalR or Supabase.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with SignalR?
What tools integrate with Supabase?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to SignalR and Supabase?
Firebase
Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.
Pusher
Pusher is the category leader in delightful APIs for app developers building communication and collaboration features.
RabbitMQ
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
WebRTC
It is a free, open project that enables web browsers with Real-Time Communications (RTC) capabilities via simple JavaScript APIs. The WebRTC components have been optimized to best serve this purpose.
MQTT
It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.
See all alternatives