In order to prevent vendor/module lock-in with your real-time system I would 
suggest using http://github.com/primus/primus as
a wrapper on top of Engine.IO/Socket.IO or what ever you decided to use. Primus 
actually fixes a lot of issues that people see
when they are using Socket.IO and these other real-time systems. For Socket.IO 
we completely ditch the build-in namespacing to bypass handshake and 
reconnection bugs and use the internal Socket directly for communication which 
improves performance as well as an increased of stability. If you feel that 
Socket.IO was a bad choice for your project, it's literally 1 single of code 
that you need to change to support a different real-time framework. No need to 
completely rewrite your app, just 1 line, 1 word and you're done.

Also I quickly scanned through the blog post the lightstreamer blog and it's 
clearly focused on to bashing Socket.IO. It's quite unfair to just plainly 
write a timestamp value vs emitting a timestamp event + arguments on Socket.IO. 
Also it's known that the RedisStore in Socket.IO causes high latencies and 
increases the broken connections. In addition to that, it was never officially 
announced by Socket.IO.

(I'm not saying Socket.IO is awesome, because it's not, i'm merely saying that 
it's unfairly judged in the blog) 

On Wednesday, October 2, 2013 at 3:49 PM, Valerio Celletti wrote:

> Hi Nikola,
> 
> 
> My 5 cents - have you taken other solutions in consideration? Simone Fabiano 
> recently issued here 
> (http://blog.lightstreamer.com/2013/05/benchmarking-socketio-vs-lightstreamer.html)
>  an apple-to-apple data broadcasting comparison with socket.io 
> (http://socket.io) (messages generated on the server side and sent to over 4 
> thousand clients, ran over two Amazon EC2 Machines) and it proved to be able 
> to scale better than plain websockets with socket.io (http://socket.io) in 
> CPU usage, data latency, and bandwidth consumption, with some other useful 
> features to improve the overall performance. The same benchmarking kit has 
> been left on GitHub 
> (https://github.com/Weswit/Lightstreamer-toolkit-Socket.IO-benchmark), so you 
> can get it and test other scenarios. Note that a startup program 
> (http://www.lightstreamer.com/startup), which allows to get Lightstreamer at 
> special conditions, is currently active.
> 
> 
> 
> Hope that helps,
> Valerio
> 
> [full disclosure: I work for LS]
> 
> 
> On Tuesday, April 16, 2013 12:03:11 AM UTC+2, Salines wrote:
> > Hi, I need your advice.
> > 
> > I primarily use CakePHP for web development, but now I need to choose 
> > technology for my startup project.
> > 
> > Web applications must be implemented with real-time notification technology.
> > 
> > I am in doubt , to create a complete project using nodejs + express, or use 
> > nodejs + socket.io (http://socket.io) for broadcast notification, and for 
> > the rest of the application using CakePHP or Ruby on Rails.
> > 
> > My project is targeting to a very large online community with hundreds of 
> > thousands of members.
> > 
> > thanks
> > Nikola
> -- 
> -- 
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: 
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected] 
> (mailto:[email protected])
> To unsubscribe from this group, send email to
> [email protected] 
> (mailto:[email protected])
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>  
> --- 
> You received this message because you are subscribed to the Google Groups 
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> (mailto:[email protected]).
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to