My company is rolling out a large application that involves several backend microservices. The development team is looking for a way to provide a single endpoint that can route requests to the different services based on the request paths. Although I have concerns about this approach, I went ahead and set up an HAProxy Ingress Controller for L7 routing within our cluster. I'm wondering if this is considered a bad practice and what better options we could explore instead.
5 Answers
Traefik handles this kind of setup excellently—no need to overcomplicate things. Also, check out Gateway API and wildcard certificates for your routes.
It's pretty standard to have a unified DNS entry point for multiple microservices. We handle this by organizing services under specific domains, like everything for platform X is accessed through platformXName. We're currently using path-based routing with Traefik, and I think any L7 controller with that capability works well. Just a heads up, I'd avoid Nginx since its open-source version is being phased out.
You could definitely use an ingress like the HAProxy ingress controller or a load balancer from your cloud provider to manage path-based routing. Honestly, I think exploring Envoy might be beneficial too!
Traefik does a great job at this, and I’ve had luck with KGateway for more complex routing needs. Have you thought about using APISIX Ingress Gateway? It's a solid choice with dynamic configuration support.
Have you considered Istio with the Istio Ingress Gateway? It can offer some advanced features and might suit your needs.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically