It might be you're correct in general. The last few years, my team has worked with go fairly extensively for this sort of work, and it is a single line of go an

It might be you're correct in general. The last few years, my team has worked with go fairly extensively for this sort of work, and it is a single line of go and a very short nginx block to get running. I think the difference was that django wanted python running through WSGI; the go servers expect to be running behind the scenes and just using nginx as a proxy.