problem description
recently developed an API micro-service interface with go gin, and now want to deploy it online to provide services to app
the original plan was to let app visit http://ip:9000
directly.but colleagues say that nginx should be used as a reverse proxy, so that the performance will be higher.
in this case, the deployment mode becomes app to access http://a.com/api. After receiving this request, nginx reverse proxies to the local
http://127.0.0.1:9000
questions
1. If the number of visits is very high, will the performance of directly accessing the go service port be high, or will it be high after being proxied by nginx?
2. If nginx proxies go services with higher performance, why is it better with one more layer? is it similar to the relationship between nginx and php-fpm?