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.
External reviews
External reviews are not included in the AWS star rating for the product.
An invaluable tool for teams looking for hassle-free, cloud-native reverse proxy implementation
Flexible, easy to use Load Balancer for everyone
Great for small and large projects
Though it has a steep learning curve, Traefik has powerful tools for routing among docker containers
Extensive proxy for all use cases!
The comprehensive documentation provided by Traefik is another major advantage. It’s well-organized, detailed, and covers virtually every possible use case. Whether you’re just getting started or diving deep into complex scenarios, the documentation is a reliable resource. It walks you through configurations, best practices, and even troubleshooting, ensuring that you can make the most out of Traefik's extensive capabilities.
Moreover, Traefik is incredibly flexible and can be used in almost any environment or use case. It supports a wide range of orchestrators like Kubernetes, Docker, and more. This versatility allows it to fit seamlessly into various infrastructures, from small-scale setups to large, complex systems. Whether you need to manage traffic for a single application or a sprawling microservices architecture, Traefik is equipped to meet the challenge.
Overall, Traefik’s extensive configuration options, robust documentation, and wide applicability make it an indispensable tool for anyone looking to efficiently manage their network traffic in a scalable and secure way.
However, once you get past the initial learning curve, the flexibility and control that Traefik offers are unmatched. The comprehensive documentation helps mitigate this complexity, guiding you through the setup process and helping you understand how to tailor Traefik to your specific needs. With time and experience, you'll likely find that the initial complexity is a small price to pay for the robust and customizable infrastructure that Traefik enables.
Efficient and Flexible Service Management with Traefik
For me, Traefik’s ability to dynamically discover and configure new services is a game-changer. It eliminates the need for manual configuration every time a new service is added, which not only saves time but also reduces the risk of configuration errors. Additionally, its built-in support for HTTPS with real signed certificates ensures that all my applications are secure without extra hassle.
Fast and powerful reverse proxy with everything you need for your containerized infrastructure
One of the best parts about Traefik is that it includes a ton of functionality baked into the service, like automatic SSL certificate generation for your web applications and middleware to manipulate incoming requests. You don't need to deal with plugins or additional software nor modify your applications, and configuring them is straightforward. Having a lot of these systems in a single place helps managing things a breeze. The included dashboard is also useful to see your complete setup.
Debugging issues can be a bit of a challenge at times, especially when involving more complex setups of routers and middleware. With all the points where something can go wrong and sometimes-unclear error logs, fixing problems when they arise can take quite some time to deal with.
- Managing routing rules for microservices to allow me to handle where my incoming traffic goes.
- Simple service discovery for new Docker containers which lets me add new microservices without needing additional configuration.
- Automatic SSL certificate generation so I don't have to worry about renewing them.
- Easy-to-add middleware options for rate limiting and basic authentication when needed.
Traefik通过提供高效的流量路由和服务发现来简化我们的交付。
1. Automatic Service Discovery and Configuration: Traefik can automatically discover services and generate routing rules based on configuration. This greatly simplifies service management in a microservices architecture.
2. Multi-Backend Support: Traefik supports multiple backends, including Docker, Kubernetes, Mesos, etc., allowing easy integration into different environments.
3. Rich Routing Rules: Traefik offers flexible routing rule configuration, enabling routing based on various conditions such as domain names, paths, request headers, and more.
4. Plugin Mechanism: Traefik's plugin mechanism is very powerful, allowing for functionality extensions such as authentication, authorization, logging, monitoring, etc.
5. High Performance: Developed in Go, Traefik features high performance and low latency.
1. Configuration Complexity: Although Traefik offers automatic configuration features, the configuration can still be quite complex for intricate routing rules and advanced functionalities.
2. Learning Curve: For beginners, it may take some time to master all the features and configuration options of Traefik. Additionally, there are relatively few resources available, especially in the Chinese community.
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?
The middleware feature makes all the difference
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.