(Disclosure: I’m the VP Eng at Jut) As Dave pointed out in the blog, we’ve definitely run into our fair share of challenges with the inherent limits of node.js

(Disclosure: I’m the VP Eng at Jut) As Dave pointed out in the blog, we’ve definitely run into our fair share of challenges with the inherent limits of node.js. But on the whole, we’ve found it to strike a good balance between speed of development and performance. In addition to some of the techniques talked about in the post, we’ve also dropped down to C++ add-ons where we have really critical performance sections, and we do coarse-grained load balancing between multiple node processes to distribute computation on multiple cores. We also have a good bit of shared code between the browser and server (including the Juttle language compiler and runtime) that has been hugely beneficial for us. YMMV of course.