News for hackers. Stuff that matters.
Re:You might not need a WebSocket by lionheart on Thursday July 10, 2014 @12:37PM (#8015587)
So I'm curious, what's the difference between fanout.io and something like pusher.com?

My company's application has some real-time components and we've just been using pusher to handle it because it's simple and cheap. Is fanout something I should consider instead?

Re:You might not need a WebSocket by jkarneges on Thursday July 10, 2014 @12:51PM (#8015679)
Fanout's great for powering a public-facing realtime API. For example, you can see what Superfeedr did with it here: http://blog.superfeedr.com/stream-superfeedr/

If you're not making an API, and you're just pushing data to your own client applications that you control, then Pusher and Fanout are more or less the same. Although you might like Fanout's simpler pricing model and our more open philosophy.

Re:You might not need a WebSocket by lionheart on Thursday July 10, 2014 @02:19PM (#8016240)
That sounds great actually. We don't have an API now but we're planning to start one in the next 30 days and I was wondering about how we were going to do the real-time aspect.

I'm going to bookmark this.

Re:You might not need a WebSocket by johne20 on Thursday July 10, 2014 @01:37PM (#8015980)
What would be the best technology for building real-time browser based chat application available today where I own the client?
Re:You might not need a WebSocket by jkarneges on Thursday July 10, 2014 @02:06PM (#8016151)
I think I'm too biased to answer this properly. :) All of the realtime-as-a-service options have good resiliency. Pair one of them with RESTful AJAX for the chat db/logic and you'll do well.