News for hackers. Stuff that matters.
Re:So you want to expose Go on the Internet by jest7325 on Monday December 19, 2016 @02:17PM (#13214138)
I wonder if it would make sense to front-end that with nginx. It has nice http2 and the latest SSL/TLS implementation. Just curious what other think about this approach.
Re:So you want to expose Go on the Internet by toufka on Monday December 19, 2016 @02:26PM (#13214242)
That's currently what is done. However the idea that I could get my entire stack, from HTTP handler, to router, to logic, to database query, back to response into a single 10mb binary is pretty enticing.

If I could get there, I'd have full control over every aspect of an API request from packet to server query, back to payload, in a single programming language, in a single conceptual framework. There is a lot to like about that. I'm not sure it's needed - nginx works so well, and perfect settings are just a single config file away. But if I could get to a truly single-binary deployment, I'd be pretty happy too.

Re:So you want to expose Go on the Internet by kevinburke on Monday December 19, 2016 @02:19PM (#13214171)
literally the first sentence of the post:

> Back when crypto/tls was slow and net/http young, the general wisdom was to always put Go servers behind a reverse proxy like NGINX. That’s not necessary anymore!