3 ms·
Great! You've made yourself a haproxy. The next step would be to make it dynamically configurable at runtime. Then there needs to be monitoring. And some tools
by xorcist 6y ago
Great! You've made yourself a haproxy.
The next step would be to make it dynamically configurable at runtime. Then there needs to be monitoring. And some tools for troubleshooting.
There's something to be said for battle hardened tools.
- sgt 6y agoHow flexible is haproxy though? We recently started writing our own API gateway because we needed tight integration to existing services, even support some specific legacy authentication schemes.
- mlinhares 6y agoIt's better nowadays, specially if you go for the paid version, I think they saw the writing on the wall that they wouldn't really have a future proof business if they kept on the "config file for everything" mantra, there's even a prometheus module you can bundle so you don't have to use the horrible metrics they had. I think it's pretty good people are building these proxies as it's forcing the entrenched vendors to move.
- xorcist 6y agoIntegrations are never maintenance free, however I found them much easier to write than to get a greenfield proxy up to snuff. It can call out to lua functions nowadays, but I haven't had to use that yet.
- digianarchist 6y ago>The next step would be to make it dynamically configurable at runtime. Like Caddy? https://caddyserver.com/ https://caddyserver.com/
- mholt 6y agoYeah, Dgraph is doing exactly this, building their own gateway as Caddy modules: https://twitter.com/caddyserver/status/1349434660107939841 https://twitter.com/caddyserver/status/1349434660107939841 > I'm impressed with how easy this was. I think I'm starting to understand why Caddy is not just a proxy, but a system for hosting apps.