I have already read some of the questions about go and nginx but I didn't find any answer to my one.
I think (i'm not an expert) that using nginx as a reverse proxy in front of a net/http
go server is different as directly hosting your go application with nginx.
Shout at me if I'm wrong, ok?
The question came to me because I need to develop an application (possibly with go, just to learn something new) and have total control on the webserver, especially on the number of workers it uses to answer requests.
So, here come the questions:
Is it possible to directly host a go app on nginx, or is it nginx that only serves static files (if the answer is "NO", then the second question doesn't make much sense)?
What are the key differences between the two approaches above, precisely, does the different approaches affects the configuration someway?
I am scared about telling nginx: "Ok, use 8 workers, please" and telling nothing to go's internal webserver... What would happen?
Thank you so much in advance