Question + Update Docs - Why can't I just use Socket.IO-Server with kafka-node? about reactive-interaction-gateway HOT 4 CLOSED

I agree, we need some numbers that prove that claim. Indeed, we're currently preparing another round of performance tests to guide upcoming performance optimizations, and also talked about applying the same tests to the Node based implementation. We'll publish the results in another blog post. Thanks for the suggestion!

from reactive-interaction-gateway.

I'm not sure what you mean... could you please elaborate? Not sure if you're saying that a nodejs, socket.io based server is easier or harder to scale than RIG...

from reactive-interaction-gateway.

In the blog post you mention an initial node implementation:

Our first prototype was written in Node.js. The app worked, but scaled very poorly in both directions.

Some more details on the scaling issues encountered would be helpful.

from reactive-interaction-gateway.

We had some discussion around this: socket.io has it's own non-standard protocol and we really don't want to rebuild it here. It also serves a very real-time purpose (think live chat) while the RIG is about a reactive architecture where updates naturally flow in.

from reactive-interaction-gateway.