This is an excellent article which really highlights the underlying trade-offs when you choose node for your service (i/o bound work vs cpu). Unless you know f

This is an excellent article which really highlights the underlying trade-offs when you choose node for your service (i/o bound work vs cpu). Unless you know for sure what limits you will hit - it makes sense to iterate quickly and find out. Then, if the service is actually hitting limits (and probably not the ones you thought) - re-write it in a multi-threaded concurrent language like go, elixr etc - or a language designed to solve the actual problems the service is hitting (which might be disk i/o or other infrastructure level things not language choice)