<p>I am about to deploy a HTTP api written in Go and are looking into how people do that practically.</p>
<p>I have noticed that some people use Nginx in front of Go, but I do not understand what the benefits are. Go can do all that Nginx can do and to me it just looks like adding another layer of complexity.</p>
<p>Arguments such as using Nginx as a load balancer seems more theoretical that actual practical implementation, ie. people are saying this, but not actually doing it. I think this could be handled much better at the DNS request level instead.</p>
<p>I also find that Go handles HTTPS very well and it is extremely easy to deploy.</p>
<p>Any input from real life experience in deployment would be greatly appreciated.</p>
<hr/>**评论：**<br/><br/>very-little-gravitas: <pre><p>You don't need a reverse proxy in front of your go process, but it can be handy for things like terminating tls and cert handling, handling several domains on one server, graceful restarts, serving static assets, redirects/rewrites, that sort of thing. Of course you could do everything in your app by writing it yourself but sometimes it's easier to put your go binary up as a service sitting behind a proxy, particularly if you have more than one service on a server. For an API you may find you don't need any of the above, but it can be handy. </p>
<p>If you want https, you could also try Caddy Server as a reverse proxy. You'll get free https from letsencrypt with certs automatically requested for your domain (this bit is really nice, uses the lego library) and it takes very little memory.</p>
<p>I'm running <a href="https://golangnews.com">https://golangnews.com</a> with this config (go process behind Caddy) on a $5 DO instance, and it seems to be doing fine so far (have only recently switched from nginx as an experiment, as usually that's my first choice).</p></pre>iends: <pre><p>Thanks for sharing your site!</p></pre>Midnightblues: <pre><p>What is your Caddyfile like? I've been trying to run a go web app through Caddy and have been running into some problems, and haven't been able to find much on serving a web app and not just a static website.</p></pre>NocturnalWaffle: <pre><p>Here's a Caddyfile that I'm using for some stuff I was messing around with. The first one is the basic serve from a directory, the second is the recommeding settings for Gogs (git web host written in go) and the last is a proxy that serves as an easier to remember url with a password on the front of it. All the tls parts have my email so it uses that to auto renew. You could also pass it in at the arguments to start it, but I just haven't added it to my init script. </p>
<pre><code>mysite.com {
tls email@example.com
root /www/mysite.com
}
git.example.com {
tls email@example.com
proxy / http://localhost:3000 {
except /css /fonts /js /img
}
root /home/git/gogs/public
log git.access.log
}
sub.example.co {
tls email@example.com
proxy / http://otherwebsite.com
basicauth / me password
}
</code></pre>
<p>Essentially, you just start your application on a different port and do a local proxy to it. You can exclude certain directories like in the git example so the webserver can handle the static content, as it in theory is better at caching and serving it. </p></pre>very-little-gravitas: <pre><p>Here is an annotated version, hope that helps. If you're having problems perhaps try starting caddy manually (not as a service) to see what it does on startup, and you can omit the tls and set the port of the vhost to :80 to eliminate that part. </p>
<pre><code>golangnews.com {
# location of static files on your server
root /srv/mypath/golangnews.com/public
log /srv/mypath/golangnews.com/log/access.log
# enable gzip
gzip
# use tls, create or renew cert if necc
tls example@example.com
# for / serve from the port at which the backend serves the website
proxy / :9999 {
# except some things for caddy to serve directly
except /assets /files /robots.txt /favicon.ico
}
}
</code></pre></pre>skmetaly: <pre><p>Thanks man ! this really got me going with Caddy seeing how dead simple the Caddyfile is </p></pre>WellAdjustedOutlaw: <pre><p>Don't use DNS (only) for load balancing. It won't work the way you expect.</p></pre>nate510: <pre><p>A thousand times this. Load balancing with DNS means that in practice a single noisy consumer will only be hitting one of your API nodes at any time, due to DNS caching. I have experienced this in practice when consuming badly deployed APIs.</p>
<p>A reverse proxy like Nginx is crucial for evenly distributing traffic to your origin servers. If you are on AWS, you can use their Elastic Load Balancing service, which saves you the hassle of maintaining your own reverse proxy deployment.</p>
<p>We run a small service with 2 haproxy nodes with round robin DNS backed by 2 origin servers. This setup provides good redundancy and effective load balancing.</p></pre>kd8aqz: <pre><p>Yes - load balancing is so much more than just making sure more than one node can receive requests. I'm also using 2 haproxy nodes but with a virtual IP on each and another piece of software (the name is escaping me) to migrate IPs when necessary. The idea being that DNS round robin is between the VIPs and those are always available, even if a node is down.</p></pre>rajoberoi: <pre><p>Hi!</p>
<p>Built-in Go server is great for an API-only setup. Needs supervisor sort of script setup to handle crashes/reboots.</p>
<p>I have a domain.com serving a static website via nginx and an api.domain.com serving the Go app via proxy. The nginx conf is convenient to setup redirects. Multiple sites can have a common.conf file. For example if you want to redirect http traffic to https. </p>
<p>I also find tailing nginx access and error logs great for monitoring every request that hits the server. </p></pre>JimBlizz: <pre><p>I'm interested in this too.</p>
<p>I think the idea is to use Nginx in front to server static assets more efficiently. Though I wonder if Varnish would be a better option for that?</p></pre>ngrilly: <pre><p>Caddy is quite efficient compared to nginx and is written in Go:</p>
<p><a href="https://caddyserver.com/">https://caddyserver.com/</a></p></pre>tedreed: <pre><p>I actually found that for static assets just using ServeFile was faster than nginx for a work project. We (I) ended up making a very very simple fileserver called fastserve. I was thoroughly surprised that it was faster.</p>
<p>(Although I think I did end up disabling mime-type autodetection to make it faster, I'm pretty sure it was already faster than nginx before I did that.)</p></pre>koalefant: <pre><p>I remember seeing benchmarks suggesting it was slower but I'm on mobile atm</p>
<p>One thing I do like about nginx though is that in html files you can just specify the filename and nginx regex match image files to a directory, whereas in Go I would have to specify the path of the image since the default mux has only a simple route matching capability.</p></pre>aaaqqq: <pre><p>I use Nginx in front of a Go app mainly because it is more widely used and hence is more 'battle tested'. A side benefit is that Nginx is also great for serving static assets if required. </p>
<p>Edit: Another reason could be if want to serve multiple applications on the same server over port 80.</p></pre>sofaofthedamned: <pre><p>I use haproxy in front of everything as it means my ssl certs are only in one place, not many.</p></pre>floralfrog: <pre><p>A few thoughts: I have both setups running on different projects right now: a small Go API that exposes itself (no nginx in front) and a different project where multiple Go programs are set up behind nginx, which acts as a reverse proxy. </p>
<p>Both work great and I think it depends on the complexity of the rest of the system. My nginx setup routes most traffic to a Rails app, some routes go to static file handlers, and some to different Go services. I think as soon as you have different routes that should be handled by different processes, you need some kind of reverse proxy, and I would not re-implement that in Go. But if you have something like <code>api.example.com/foo/bar</code> and all routes on the api sub domain are part of your Go app, it is easier to expose it directly.</p>
<p>The Go http packages in the stdlib are designed to not need an additional layer in front, so there is no problem with that. Especially now with http/2 being supported, there is less of a reason to put nginx in front. But to me nginx just <em>feels</em> like this rock solid "thing", refined over many years, that just sits there and whatever you throw at it, it keeps going. Not sure if I can say the same about my Go programs (yet).</p></pre>gohacker: <pre><blockquote>
<p>multiple Go programs are set up behind nginx, which acts as a reverse proxy. </p>
</blockquote>
<p>This. Go and not Go servers sitting behind the reverse proxy using a single port.</p></pre>program_the_world: <pre><blockquote>
<p>This. Go and not Go servers </p>
</blockquote>
<p>I'm having difficulty understanding this part of your comment. Could you please explain?</p></pre>DownGoat: <pre><p>Your whole setup might include different applications, some in Go, and some in other languages.</p></pre>program_the_world: <pre><p>Ahh now I see it. Thanks for explaining.</p></pre>raerius: <pre><blockquote>
<p>Arguments such as using Nginx as a load balancer seems more theoretical that actual practical implementation, ie. people are saying this, but not actually doing it. I think this could be handled much better at the DNS request level instead.</p>
</blockquote>
<p>Ok. So you suddenly exhausted the resources of your server. Think optimization issue or reddit hug of death. You need more resources STAT. Great, set up another server on a new IP and enter this IP into DNS. Then you wait for TTL seconds before clients can possibly hit your new server.</p>
<p>And what about maintenance? Do you remove a record from DNS and wait for traffic to slowly migrate to a different IP before you take one of your machines down?</p>
<p>Or would you rather just spin up a new VM (or provision some new iron), dump your binary and config on there and (if you happen to run NGINX Plus) just have the binary register itself with the load balancer and watch everything work as if by magic? </p>
<p>Replace nginx plus with community version and your config management of choice. Personally I use saltstack for my small-ish setup.</p>
<p>Sure, you get a certain amount of load balancing with DNS RR, but it is far from optimal and you're lacking proper HA.</p></pre>mc_hammerd: <pre><p>Semi educated guess that:</p>
<p>Nginx is chosen:</p>
<ul>
<li>to serve static directories and assets</li>
<li>assumed to be faster than go's built in server</li>
<li>has cache for these one config line away (or admin already knows how)</li>
<li>assumed to be more secure and battle-proven than go's webserver</li>
<li>doesnt expose hypothetical vulnerabilities of go's webserver past /index and /websocket </li>
<li>assumed to have better ddos protection than go's webserver (by me i guess?) ex: the common ddos of last year was opening a bunch of unfinished HTTP req's "GET /longurl___no new line",</li>
</ul>
<blockquote>
<p>i think its all hypothetical, go has had no sever vuln's posted yet</p>
</blockquote></pre>tvmaly: <pre><p>IF you happen to have a couple of microservices running on different ports, using NGINX gets rid of the CORS for you. Since everything would be proxied through a single port, the domain would match.</p></pre>koffiezet: <pre><p>The main reasons why I'd go for a reverse proxy setup for HTTPS/SSL are:</p>
<ul>
<li>better tested crypto backends (e.g. no timing attacks, to which the go implementation - at least up to a certain point - was vulnerable)</li>
<li>No recompiling of backend(s) when critical SSL implementation bug is found. Update reverse proxy, done.</li>
<li>Centralized SSL certificate storage</li>
</ul></pre>dhdersch: <pre><p>I recently tried to spin up an HTTPS server in Go without a proxy. The main caveat was that I need to perform Client Certificate Authentication. For the life of me, I couldn't get this to work. It was much easier to put Apache in front of it.</p></pre>j1436go: <pre><p>I used a Go server as reverse proxy in front of several services that are reachable on different subdomains and was totally happy with it. But then i had the need to serve an app with fcgi and that's when i switched to nginx.</p></pre>codepushr: <pre><p>I think that Go alone should work out fine. I too have deployed my first go service in production a few months ago. In our case we already had Apache running because of our landing page and Wordpress blog, so port 80 was already reserved. I already had defined dozens of virtual hosts, so I simply created another one with Go using the mod_proxy module.
I think using another http software that can act as a proxy makes sense if you got other instances running in your environment like other services, blogs... and want to wrap them.</p></pre>JacksGT: <pre><p>Does go already support HTTP/2?</p></pre>varun06: <pre><p>It is part of 1.6 release. but you can test it currently.
<a href="https://github.com/golang/net/tree/master/http2" rel="nofollow">https://github.com/golang/net/tree/master/http2</a></p></pre>JacksGT: <pre><p>Ah, good to know.</p>
<p>Thank you!</p></pre>rem7: <pre><p>I like to put nginx infront of my Go web apps as well. Can go do everything that nginx can? Sure. Some things I'd have to code. Nginx already has a lot of built in functions that I really don't want to write in Go, and the nginx team has done a better job than I will. Things I use nginx for:</p>
<ul>
<li>TLS Termination </li>
<li>Basic logging</li>
<li>Cache settings</li>
<li>gzip module</li>
<li>static files </li>
</ul></pre>journalctl: <pre><p>Don't forget rate limiting. Easily protect your log in page from getting brute forced and just in general stopping obviously malicious requests from even making it to your backend. </p></pre>AnimalMachine: <pre><p>I'm late to the party, but I also run my go app servers behind a nginx reverse proxy. It doesn't take much to setup nginx, SSL setup was fairly easy and I can respond to multiple hosts via virtual host setups by redirecting traffic to each web app's hidden port.</p>
<p>Yes, I could have done it all with Go. But nginx is battle tested, can load ballance if I need it, and fairly painless to maintain for a small setup. Besides, sometimes adding another layer of complexity isn't all that bad for security.</p></pre>YuryOdin: <pre><p>You need to use nginx in front of Golang http server.
Because in Golang<=1.6 have slow AES algorithm.</p></pre>program_the_world: <pre><p>How can it be slow? Surely it utilizes hardware acceleration? </p></pre>very-little-gravitas: <pre><blockquote>
<p>You need to use nginx in front of Golang http server. Because in Golang<=1.6 have slow AES algorithm.</p>
</blockquote>
<p>Did you mean https? http doesn't use AES. Also, this does depend on load, I imagine most services won't find the speed of tls a problem. </p></pre>YuryOdin: <pre><p><a href="https://blog.cloudflare.com/go-crypto-bridging-the-performance-gap/">https://blog.cloudflare.com/go-crypto-bridging-the-performance-gap/</a></p></pre>very-little-gravitas: <pre><p>Most of us don't operate anywhere near the scale of cloudflare, so while it's nice to see it getting faster, it is not usually a problem.</p></pre>mannix913: <pre><p>The reality is that most TLS/SSL termination will be done on a load balancer and not on the app servers themselves unless you have a special need. Ideally all connections would happen over TLS no matter the destination. </p></pre>jamra06: <pre><p>As Nginx keeps on pushing their Plus version, it is increasingly necessary to keep the capability in our hands. </p></pre>ecmdome: <pre><p>This is pretty awesome gonna look more into it </p></pre>
