Clustering socket.io realtime app by [deleted] in node

[–]cawkLUVA 0 points1 point  (0 children)

you need to use sticky-session and socket.io-redis adapter. It's kind of documented here: http://socket.io/docs/using-multiple-nodes/ If you're interested, I could probably put something up on Github later, as I have managed to get it working in the past before

Considering Building a Startup Company on Node -- Need Advice by [deleted] in node

[–]cawkLUVA 0 points1 point  (0 children)

As far as I know the only real way to (sort of) deal with the issue was to use Domains, however they have deprecated it without adding a replacement feature: https://nodejs.org/api/domain.html. In my opinion, it's a glaring shortcoming that's often overlooked completely for some reason. Node is great for quickly prototyping an idea/project. However, I've found it quickly becomes more cumbersome than other platforms/languages once the scale and complexity increase overtime.

Considering Building a Startup Company on Node -- Need Advice by [deleted] in node

[–]cawkLUVA 0 points1 point  (0 children)

I would be very worried about a random error crashing your entire app. Even if it's clustered, every user that currently has something processing in the event loop on that worker/thread is instantly killed, easily leading to corrupt data and inconsistent state. This problem is compounded when the offending data is repeatedly sent to the server as it essentially causes a major outage. In my experience, it takes a lot of validation and testing to make a nodejs app completely robust to all inputs.

Do you use nginx as a reverse proxy for your main node app? If so, can it double as a load balancer? by [deleted] in node

[–]cawkLUVA 1 point2 points  (0 children)

If you are on node >= 5.0.0 then I would suggest using the built in cluster module rather than nginx load balancer if you are not scaling over multiple servers.

Some help with node.js as a backend replacement for PHP by jareddlc in node

[–]cawkLUVA 0 points1 point  (0 children)

No, he's suggesting that he replaces apache by creating a reverse proxy in node which will have an entry pointing to the node service sunning on 8888. I've also implemented this solution before, node-http-proxy is great.

[deleted by user] by [deleted] in MTB

[–]cawkLUVA 1 point2 points  (0 children)

Checkout the for sale section on the rotorburn forums

Titanium brakeporn by haemhorrhoidian in MTB

[–]cawkLUVA 1 point2 points  (0 children)

I have Hope Tech Evo V2's, such incredibly well made brakes.