Why is NGINX unit needed for go/node.js?

Question

Nginx

How does an NGINX unit for a language that is itself a web server (meaning "not needing an application server"), such as go or node.js, differ from the traditional configuration of NGINX as a proxy in front of the application? (NGINX as a proxy vs NGINX unit in the context of "standalone" languages)

Thanks.

Answer 1

Nginx is a web server. This implies multithreading, the ability to hang many sites on one ip, and other goodies.
The node is single-threaded, all sorts of bells and whistles like webworkers are crutches, normal production under a high load can be done, but difficult (IMHO).
Try, test, load, feel the difference

Answer 2

unit has an API. You can change settings, add/remove application instances. I don't see any other uses.