3 ms·
(I work on the same site/problem as author) We would prefer node did not deal with the https, I actually did a previous blog post showing how performance degr
by beck5 14y ago
(I work on the same site/problem as author)
We would prefer node did not deal with the https, I actually did a previous blog post showing how performance degraded https://www.sharelatex.com/blog/posts/nodejs_http_vs_https.html https://www.sharelatex.com/blog/posts/nodejs_http_vs_https.h....
Options like Ngnix and haproxy without pound/stud are quite recent and we have not gotten around to trying them out.
In regards to clustering, running socket.io in a cluster with redis store is another world of memory leaking pain. Hopefully socket.io 1.0 with engine.io will solve this but its been nearly released for several months now.
I am now starting to question the value of websockets, long polling is a lot simpler in many ways and robust.
- exratione 14y agoI can recommend HAProxy based on my experiences. If you want to go with established tech over newer stuff (and the Nginx websocket support is definitely too new for me - give it another 6 months at least), then you can Rube Goldberg a fun setup with Stunnel and Varnish replacing HAProxy. http://www.exratione.com/2012/08/websockets-over-ssl-stunnel-varnish-nginx-nodejs/ http://www.exratione.com/2012/08/websockets-over-ssl-stunnel... I haven't had any unpleasant happenings myself with clustering Socket.IO and Redis; that'd be a topic I'd like to see a post on from your lot, given that I'm presently working on the cluster code for a demi-framework for clustered single page Node/Socket apps: https://github.com/exratione/thywill https://github.com/exratione/thywill
- MatthewPhillips 14y agoTurning on WebSockets in Nginx is a breeze, I definitely recommend doing so. Awesome investigative work nonetheless.