At Razorpay, the tool is used as a reverse proxy, ingress controller, and CRD management. A year and a half ago, my company started to move from Traefik Enterprise v1.0 to Traefik Enterprise v2.0. The tool handles everything, including the integrations with our different cloud providers and some of the other features we use in our company, such as rate limiting, which is something that is available within Traefik Enterprise.
Traefik Hub
Traefik LabsExternal reviews
35 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Offers a good dashboard that provides a great overview to users
What is our primary use case?
What is most valuable?
The most valuable feature of the solution stems from the fact that ingress management is way easier in Traefik Enterprise, and there are many tools present within Traefik Enterprise's repositories, which allowed us to easily transition to it. The tool's dashboard is very helpful in handling any issues that we might face as we get a very good overview straight up from Traefik Enterprise's dashboard, which helps us debug or do anything during any sort of production issue.
What needs improvement?
I would say that maybe along the same path that Traefik Enterprise is currently on, you have most of the things straight up in the UI that you can check even with minimal training. You can just use, understand, and debug things from the UI. There is still work to be done in the tool, which can ensure that anyone with just minimal know-how of the product doesn't have to really go into the terminal and see the status of routes, concierge routes, or whether certain things are up or not. One should be able to just check things straight up from the UI and get to know what kind of issues are there in the solution, and even though such a feature is already there in the tool, there is more work to be done in it.
I would not particularly recommend any improvements when it comes to the security of traffic. I think the tool is pretty pluggable in terms of whatever security we want to put in our routes, even though it is just as a middleware or just as a supporting product for whatever we have in our services.
For how long have I used the solution?
I have been using Traefik Enterprise for two and a half years. I am a user of the tool.
What do I think about the stability of the solution?
It is a stable solution. Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
The tool handles scalability pretty easily. Adding more instances of services and all are pretty intuitive to do using Traefik Enterprise.
There is a dedicated DevOps team in my company that basically is the first line for anything to do with dashboards or the onboarding of a new service onto it. Everything is handled by dedicated teams in my company, but other than that, every team has some people who work on the infra side. I would say that more than 100 people use the tool in my office.
Which solution did I use previously and why did I switch?
My company has used Envoy in the past.
How was the initial setup?
When my company was moving from Envoy to Traefik Enterprise, the tool's initial setup phase was a little difficult to manage in the beginning. Earlier, we had Traefik Enterprise v1.0, and then, eventually, we moved to Traefik Enterprise v2.0. Now, there is Traefik v3 as well. When moving to Traefik Enterprise v2.0, I felt the transition itself was a little bit difficult, but it was relatively smooth once the entire activity was completed.
The solution is deployed using AWS cloud services.
What's my experience with pricing, setup cost, and licensing?
One of the reasons why my company moved from Envoy, as well as the other in-house options, to Traefik Enterprise was because doing many things in-house was overkill. Traefik Enterprise was a relatively cheaper option for my company. I would say that Traefik Enterprise is cheaper than the other alternatives in the market.
What other advice do I have?
The API gateway functionality in Traefik Enterprise has improved our operations. With Envoy, managing all the routing and monitoring was much more difficult. Moving to Traefik Enterprise has made things easier for the ops teams in my company.
I have not yet integrated Traefik Enterprise with any type of AI.
My recommendations to someone depending on their use case and requirements. What AWS provides is good enough for you, and if the costs are also good enough for you, then you can stick to it. In our company's use case, we found Traefik Enterprise to be the most suitable tool for our environment. Everything depends on the particular scale that you are looking at or the particular type of API gateway functionalities that you need for your services, as well as what middleware functionalities you might need or what you might have in-house for yourself.
When I say a beginner, the whole realm of handling API gateways and service middlewares, I would say it is not a very beginner-friendly domain itself, but assuming that someone who has recently ventured into such areas but is experienced in general, then it should be pretty intuitive for them to use Traefik Enterprise.
There is some scope for improvement in the way a lot of things can be managed straight up from the UI. For power users, the tool is very intuitive, so I would say it is a pretty good product.
I rate the tool a nine out of ten.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
The middleware feature makes all the difference
What do you like best about the product?
I'm very pleased with how well Traefik follows the Kubernetes Gateway API. They have added an elegant extension point to host their great middleware feature. I believe that this approach can make it to the standard.
The move to WebAssembly for the middleware is strategically smart because it will widen the community and makes middleware execution more efficient. But it is also key in standardising middleware.
The move to WebAssembly for the middleware is strategically smart because it will widen the community and makes middleware execution more efficient. But it is also key in standardising middleware.
What do you dislike about the product?
I haven't come across any issues yet. It just works.
What problems is the product solving and how is that benefiting you?
The Traefik Proxy is the external entry point for our Kubernetes clusters on AWS EKS. All external traffic to the services is routed through and balanced by Traefik Proxy. In combination with the external-dns and cert-manager projects, it also carries and terminates the public domain names we expose. Lastly, we have created an OpenID Connect middleware, that intercepts all requests and drives the authentication of the end-user.
Running with minimal maintenance and config for years
What do you like best about the product?
I chose Traefik for work at first, building a Docker Swarm serviced by Traefik for ingress to the many websites therein. I could very easily template my compose files with the appropriate configuration, and required nearly zero maintenance on the Traefik stack for the life of the swarm.
When I refreshed my homelab, I chose Traefik for the same reasons, and I've been running it ever since. Not only was moving from v1 to v2 super easy, it's been even more stable and hands-off.
When I refreshed my homelab, I chose Traefik for the same reasons, and I've been running it ever since. Not only was moving from v1 to v2 super easy, it's been even more stable and hands-off.
What do you dislike about the product?
There's a fair bit to initially know and understand for proper setup, but documentation is pretty excellent.
What problems is the product solving and how is that benefiting you?
Easy container routing for webhosts and other similar concerns.
The Way of the Cloud Native Proxy/API Gateway master
What do you like best about the product?
Ease of Integration: Would be as easy as changing the ingressClassName
Ease of Implementation: A comprehensive Helm Chart is provided
Customer Support: I found the documentation more than adequat to get me going and very useful examples are provided
Frequency of Use: I use this product everyday as it is my go to for all things Cloud Native Proxy/API Gateway
Dynamic Configuration: Traefik excels at automatically discovering and configuring routes. It integrates seamlessly with container orchestrators like Docker, Kubernetes, and more, meaning it can automatically update its configuration as services are added or removed, without requiring manual intervention.
Built-in Let's Encrypt Support: Traefik makes it easy to obtain and renew SSL certificates through Let's Encrypt, which simplifies the process of securing web traffic.
Ease of Use: Traefik is relatively easy to set up and configure, especially compared to more traditional reverse proxy favourites. Its configuration is straightforward and can be managed through a simple YAML or TOML file.
Metrics and Monitoring: Traefik has built-in support for Prometheus metrics and other monitoring tools, making it easier to keep an eye on the health and performance of your services.
Middleware: Traefik offers a powerful middleware system that allows for advanced traffic management, such as rate limiting, IP whitelisting, redirections, and more.
Scalability: It’s highly scalable, making it well-suited for both small-scale setups and large, complex environments.
Ease of Implementation: A comprehensive Helm Chart is provided
Customer Support: I found the documentation more than adequat to get me going and very useful examples are provided
Frequency of Use: I use this product everyday as it is my go to for all things Cloud Native Proxy/API Gateway
Dynamic Configuration: Traefik excels at automatically discovering and configuring routes. It integrates seamlessly with container orchestrators like Docker, Kubernetes, and more, meaning it can automatically update its configuration as services are added or removed, without requiring manual intervention.
Built-in Let's Encrypt Support: Traefik makes it easy to obtain and renew SSL certificates through Let's Encrypt, which simplifies the process of securing web traffic.
Ease of Use: Traefik is relatively easy to set up and configure, especially compared to more traditional reverse proxy favourites. Its configuration is straightforward and can be managed through a simple YAML or TOML file.
Metrics and Monitoring: Traefik has built-in support for Prometheus metrics and other monitoring tools, making it easier to keep an eye on the health and performance of your services.
Middleware: Traefik offers a powerful middleware system that allows for advanced traffic management, such as rate limiting, IP whitelisting, redirections, and more.
Scalability: It’s highly scalable, making it well-suited for both small-scale setups and large, complex environments.
What do you dislike about the product?
Initially the experience could be one of complexity but then what isn't as oppose to other products in this space. And when you buy any product you should read the manual. I had to slow down, allocate some learning time (Traefik training) and read the manual to grasp the human thinking and concepts behind Traefik.
What problems is the product solving and how is that benefiting you?
One of the best tricks that I found with Traefik is how easy it was to start publishing services externally because of the Automated Service Discovery and Routing. It didn't take me long once I had gotten my head around Traefik language speak to get a frontend working securely. Talking on security I was able to automate certificate implementation very quickly using Cloudflare and the built in integration to Lets Encrypt. In order to do this I used a nice piece of built in logic that Traefik provides allowing it to read a dynamic configuration file. I then simply made the certificate the default for the dashboard and for all services using Traefik as the gateway to the outside world. With the Traefik dashboard I was able to get insight into the inner workings of my ingress routes, ssl/tls and middlewares. I used GitOps to deploy Traefik with Gimlet and Fluxcd thus making it super simple to upgrade my three replicas or change my configuration all the while letting Kubernetes handle the process.
To roundoff Traefik gave me a quick setup, easy configuration, flexible and secure proxy/gateway to deploy in a matter of minutes.
You can see the process I followed by checking out my PoC documented here https://ortelius.io/blog/2024/08/08/how-to-bake-an-ortelius-pi-part-3-the-gitops-configuration/ and here https://ortelius.io/blog/2024/08/10/how-to-bake-an-ortelius-pi-part-4-cloudflare-certificates-and-traefik/
To roundoff Traefik gave me a quick setup, easy configuration, flexible and secure proxy/gateway to deploy in a matter of minutes.
You can see the process I followed by checking out my PoC documented here https://ortelius.io/blog/2024/08/08/how-to-bake-an-ortelius-pi-part-3-the-gitops-configuration/ and here https://ortelius.io/blog/2024/08/10/how-to-bake-an-ortelius-pi-part-4-cloudflare-certificates-and-traefik/
The most flexible reverse proxy
What do you like best about the product?
Traefik is a very powerful reverse proxy solution I'm currently using to simplify the access to a hundred services in my homelab.
There's tons of functionality, making it a highly configurable reverse proxy, with built-in support for Let's Encrypt.
There are a number of different ways to configure Traefik, and I particularly like the Docker integration, which lets you configure Traefik with Docker labels, very useful when you want to quickly deploy a new service and integrate it into your architecture.
There's tons of functionality, making it a highly configurable reverse proxy, with built-in support for Let's Encrypt.
There are a number of different ways to configure Traefik, and I particularly like the Docker integration, which lets you configure Traefik with Docker labels, very useful when you want to quickly deploy a new service and integrate it into your architecture.
What do you dislike about the product?
As Traefik is a highly flexible solution, it's also rather complex to understand at first. There's a bit of a learning curve, but you can get by with the help of documentation and resources available on the Internet.
What problems is the product solving and how is that benefiting you?
I needed to access my homelab easily using my domain name rather than IPs and ports, and Traefik fits the bill perfectly.
First thing you install on a fresh Kubernetes cluster
What do you like best about the product?
Traefik is the best reverse proxy you can use in Kubernetes. It supports LetsEncrypt and is able to dynamically reload ingresses, act as a reverse proxy and do load balancing. We're using it daily for all of our clusers and it has worked like a charm! Has a great community and you can ask questions with the very likely-hood of them being answered by some of the Traefik developers. I highly recommend Traefik to everybody!
What do you dislike about the product?
The learning curve might be a bit high, but still well worth it.
What problems is the product solving and how is that benefiting you?
Makes configuring reverse proxy to deployed services a breeze. Also has the ability to proxy forward TCP / UDP ports which is something might need for some more specialized services (udp ports for RTC for real-time audio/video calls, etc)
Traefik simplified our infrastructure
What do you like best about the product?
What I like best about Traefik is its seamless integration with Docker, enabling automatic service discovery and dynamic configuration. This simplifies management and deployment in containerized environments, enhancing efficiency and scalability.
What do you dislike about the product?
What I dislike about Traefik is its complexity when configuring non-containerized services. The setup can require significant customization and troubleshooting, which diminishes its ease of use and efficiency outside of Docker environments.
What problems is the product solving and how is that benefiting you?
Traefik simplifies HTTPS access by automating SSL certificate management, ensuring secure connections to our services. Its dynamic service discovery and load balancing streamline deployment, enhancing security and scalability while reducing operational overhead.
Great way to reverse proxy multiple applications on your servers.
What do you like best about the product?
Once things are setup and configured it's super easy to add or modify services especially if they are running as docker containers. A few strings of text including your entry point (subdomain) and any middleware's (authentication, etc) and you are good to go.
What do you dislike about the product?
The initial setup can be complex if you don't have much experience with containerization, your use case is atypical, or you can't find an online guide or instructions to help guide you.
What problems is the product solving and how is that benefiting you?
Being a small company with multiple services and applications running on a single server Traefik helps proxy them so that everything can be accessible, protected behind SSO and 2FA, and easy to get to using your domain.
Traefik Enterprise platform aids with Service Mesh Interface (SMI) for traffic policy on K8 clusters
What do you like best about the product?
Traefik Enterprise helps us route traffic to our applications, ensuring that our customer-sensitive data only runs in a secured environment. It keeps all malicious attacks from external traffic away from our data plane with its extensive security layer. All request calls & other transactions between cluster nodes are carried out through a splendid encrypted communication channel.
What do you dislike about the product?
Only one, the learning curve is steep. We have recently started to use the Traefik Enterprise platform to regulate our cluster traffic & keep our deployments highly available, auto-scalable and secured. With adequate time and exposure, we will be able to optimize traffic management & smooth operations.
What problems is the product solving and how is that benefiting you?
By typing a few command lines, we can deploy K8 clusters having several nodes using the Traefik Enterprise platform. It gives us exceptional visibility on our entry points, cluster inspection, error reports and service mesh status in its central Dashboard. All traffic policies & telemetries, such as service latency & error rates, are managed by its Service Mesh Interface (SMI). We can also include multiple Custom Resource Definitions (CRD) for our K8 clusters for better operability & convenience through the Traefik platform.
Traefik goes DEEP
What do you like best about the product?
Extremely versatile and powerful application.
What do you dislike about the product?
Can be overwhelming, especially for someone new to proxies.
What problems is the product solving and how is that benefiting you?
Traefik serves as a vital part of our workflow in the video transcoding business. It allows us to proxy incoming requests and gathers useful logs which can be displayed on Grafana.
showing 11 - 20