CODEWITHSUNDEEP
javascriptruby-on-railsdjangoreal-timewebsocket
meow
meow

Reputation: 28154

Real time apps: Socket.io vs Pusherapp

What are the factors you would consider when choosing between Socket.io and Pusherapp? Important considerations include: integration with existing systems like rails/django, ease of setup, ease of development.

Upvotes: 15

Views: 4877

Answers (1)

user721340
user721340

Reputation:

There are a few differentiating factors, these are:

  1. Do you want to manage the scaling and hosting of your realtime infrastructure?
  2. Do you want to receive data from your clients in realtime?
  3. Do you want to be able to interact with the data between clients?

There's basically a few different use-cases for websockets, and at present no hosted solution can offer you two of those things. The current use cases I can think of are:

  1. Server --[ WebSocket ]-> Clients
  2. Server <-[ WebSocket ]-- Clients
  3. Server <-[ WebSocket ]-> Clients

Services like PusherApp target the first use-case, as it's fairly difficult to support the other two options with a hosted service. (Read: while it's difficult, it's just a bit impractical and doesn't give you the full benefits of using websockets.)

Upvotes: 9

Related Questions