I had to move most of our apis/background-jobs to node after getting fed up with the concurrency issues that ruby had. This fixes that. Although I don't think it can compare with node/eventmachine on the performance front. But that's ok IMO in most situations.
I am thinking about moving most of our api/background tasks to ruby from node, and using node only for cases that require some sort of proxying - for example proxying an request to a private elasticsearch server after authenticating.
I had to move most of our apis/background-jobs to node after getting fed up with the concurrency issues that ruby had. This fixes that. Although I don't think it can compare with node/eventmachine on the performance front. But that's ok IMO in most situations.
I am thinking about moving most of our api/background tasks to ruby from node, and using node only for cases that require some sort of proxying - for example proxying an request to a private elasticsearch server after authenticating.