2 ms·

I think it depends on the job of the software. A client i am working with is using it successfully in some areas, not successfully in others. API's, web, some w

by czbond 11y ago

I think it depends on the job of the software. A client i am working with is using it successfully in some areas, not successfully in others. API's, web, some web back ends - it does well. Rock solid, transaction heavy, worker services - no. We have a back end service that Node just keeps barfing on (wrong use case), that gets up to 2GB process size due to promises calling promises. We're replacing it with performant golang microservice.

czbond 11y ago
To add more to this, I personally will stop using node - except for in api endpoints. Our test patterns, timing, and development time have shrunk using go vs node. JS's flexibility can cause issues. I'm using go for all api endpoints, microservices, and transaction systems. I use node for microservices in which the library structure in go isn't "formed enough" - or quick services.