4 ms·
So the idea is interesting, but I think adding something like this onto Nginx could lead to problems in the future. For what you're trying to do, I feel like i
by kyrra 14y ago
So the idea is interesting, but I think adding something like this onto Nginx could lead to problems in the future.
For what you're trying to do, I feel like implementing your reverse proxy in Go may prove to be less prone to errors. Go has ReverseProxy stuff already built in: http://golang.org/pkg/net/http/httputil/#ReverseProxy http://golang.org/pkg/net/http/httputil/#ReverseProxy
Go already has a pretty strong following doing near exactly what you are doing here with Nginx + Lua. But that would require learning a new language and screwing with infrastructure, which always is a giant pain.
- justincormack 14y agoGo is the only other way I would try to do this type of thing. Nginx has the advantage that a lof of people already have it in their stack so adding some bits of Lua incrementally is easy, while with Go you would be adding another piece of infrastructure. I don't think there are any problems, or that it is error prone. Most people are learning a new language with Lua, so take your choice.
- transmit101 14y agoI don't know anything about Go but your idea sounds feasible. As another commenter says, there is a large Nginx community and we have a lot of investment in Nginx already. But for somebody starting from scratch it may be worth considering.
- vidarh 14y agoNginx is "battle tested" as one of the most used web servers, particularly as a reverse proxy. Lua is battle tested as an embedded language for just this type of thing. In comparison, Go is a pretty much unknown quantity. I'm curious as to what problems you think that this might lead to that aren't just as likely or more likely with a Go based implementation.