> I'm having trouble finding conversations like that, regarding NodeJS. Has there been a debate about best practice? Where can I find it? Here is the thing abo

> I'm having trouble finding conversations like that, regarding NodeJS. Has there been a debate about best practice? Where can I find it? Here is the thing about high level modern interpreted languages — most of the time YOU DON'T NEED all those infinite pointless debates around what practice is the best or how we design another AbstractInstanceBuilderFactoryStrategy class etc. Most of the time NodeJS just works. THere is really almost nothing to discuss, unless you face some specific unique challenge. You just write clean single threaded code, and it just works as expected. And usually just scales horizontally to a very high volumes of traffic. And the cost of change and dev experience is sometimes infinitely better than in Java/Scala stack. https://www.zdnet.com/article/how-replacing-java-with-javascript-is-paying-off-for-paypal/ https://www.zdnet.com/article/how-replacing-java-with-javasc... Hence, you don't overthink about 120 amazing classes and interfaces in advance — you can grow your design together with the requirements. Regarding the bottlenecks — the only nodejs bottleneck is pure sync calculations, so just never block the thread with heavy algorithms and you're good to go. I'm speaking of personal experience working on loaded Java and Nodejs artifacts. It's just different, much less overheaded, way of thinking about the task and about the world.