CEO at NaoLogic Inc·

We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

READ LESS
Naologic (blog.naologic.com)
12 upvotes·3 comments·718K views
Jerry Koerkenmeier
Jerry Koerkenmeier
·
March 16th 2020 at 6:19PM

Gabriel - are you using a service mesh like Maesh (from Containous which develops TraefikEE), Istio, or NGINX as service mesh? I agree Traefik is fantastic for routing and growing quickly. But wouldn't a service mesh assist with making the microservices and APIs discoverable and have better traffic control? Or is that how you have NGINX set up fronting your services?

·
Reply
Patricia Dugan
Patricia Dugan
·
March 5th 2021 at 11:01PM

Hello, Jerry. Here's the case study we did with Naologic. Perhaps it'll be useful for you. https://traefik.io/blog/naologic-surpasses-scaling-demands-of-microservice-infrastructure-by-using-traefik/

·
Reply
Gabriel Pa
Gabriel Pa
·
March 6th 2021 at 10:03AM

We're adding Maesh in our next major version upgrade, yes. We handle service discovery via K8S API

·
Reply
Avatar of Gabriel Pa

Gabriel Pa

CEO at NaoLogic Inc