> But scaling a Socket.io application is not trivial, there are users who want a hosted solution for realtime streams so that they don't have to worry about the

> But scaling a Socket.io application is not trivial, there are users who want a hosted solution for realtime streams so that they don't have to worry about their application falling over if they get too many simultaneous connections. PubNub employee here, I agree, this is the reason. > And in terms of the speed at which the messages are routed, for the purposes of a liveblog or something of that nature, pushing everything through PubNub isn't noticeably slower than using Socket.io. We aim for 1/4 second global latency (averaging 151ms currently http://status.pubnub.com/ http://status.pubnub.com/). Great demo!