Traefik Enterprise Reviews

I use Traefik Enterprise for my daily needs, including load balancing and centralizing my cloud-native applications.

At Hoichoi, we have been using Traefik Enterprise for the last two years. We implemented Traefik Enterprise for consolidating and orchestrating the network into a single endpoint. We use Traefik Enterprise to provide a single endpoint to reach all of our services.

In our company, Hoichoi, we use Traefik Enterprise for a single endpoint. We have api.hoichoi.tv, which we point to what is called a Traefik Enterprise endpoint. Inside Traefik Enterprise, we map it with another path such as /api/services to our services service and /plans to our plan service.

Apart from that, we use it for load balancing. All of our load balancing is pointed to multiple Traefik Enterprise instances, and then we divide the traffic among them. We also use it for observability to monitor how the load is spiking up or down.

I appreciate that Traefik Enterprise offers observability and load balancing features, especially the ability to orchestrate all endpoints. I love having only one domain to connect with, such as api.hoichoi.tv, and then adding only /subscription to reach my subscription service and /plans to reach the plan service.

With the observability feature in Traefik Enterprise, I get records of traffic patterns. For example, at three o'clock in the morning, I caught a traffic spike immediately, giving me proper data about when the traffic started spiking and when the load reached its peak. This allows me to reduce my bills and not keep all of my services scaled up all the time. I can scale down the services as needed.

I primarily use the observability feature and the single-pointing orchestration for all of the microservices. I appreciate these services because they help me maintain only one domain.

Traefik Enterprise is helping us tremendously because we do not need to manage multiple service domains. For example, we do not need to manage a subscription service domain and a plan service domain separately. We know that we have one domain, and if any service is down, I can go to Traefik Enterprise observability and see which domain is down, when it went down, and how it is impacting our operations.

I would appreciate improvements to the user interface because it currently appears generic. Please add more professional elements to the UI. I need this because when I open this site in public, everyone says it was built by a college student. I would love for the UI to be professional.

For other things, you should orchestrate the features list on the home page and add other things. You should not mention everything. You should mention on the home page which feature I last used so I can go there directly without navigating through settings and multiple menus. If I use any feature repeatedly, it should appear on the home page.

I have been working with this solution for almost two years in my current field.

I remember that last night at three o'clock in the morning, my senior called saying that the traffic was getting a 404 error in the plan service. I needed data on when it started and how this issue was impacting us. I went to Traefik Enterprise observability feature and checked that after our last code merge, we were getting this error. After that, we were getting the 404 error. I checked and then reverted the changes, which is why I love Traefik Enterprise observability feature.

Overall, I give Traefik Enterprise an 8 out of 10 because it is very nice to have on my production-grade server. I suggest that you improve your UI and the features, and then it will get a 10 out of 10.

I chose 8 out of 10 because I have been satisfied with all the features I use. I reduced two points because of the UI and the requirements I need. I have already suggested what I need, and I believe it will be great for me if you improve that.

We use public cloud and deploy on AWS ECS. In ECS, we deployed the Docker file. We purchased the solution from AWS Marketplace.

I suggest that everyone use this service because of its simplicity. It provides multiple features in a single product, and you only need one subscription to use it. I appreciate that service.

I am a customer from my company's side. In the future, we will connect with Traefik Enterprise business side to make a business relationship and refer our services. Currently, we are customers.

I have been using Traefik Enterprise for the last six months. Nginx Ingress for Kubernetes has expired and nobody is supporting it anymore, but we have another alternative in Traefik Enterprise.

I am using Traefik Enterprise for Ingress Kubernetes to proxy our applications from clients to our services. I work just with clouds, so all of them are installed on the cloud. I have an on-premise private server where I installed Traefik in Kubernetes, and one on-premise from my client where we are using Traefik as well.

Traefik Enterprise helps with proxying our applications because otherwise, you need to install something heavy like Ingress Kubernetes or Istio service mesh. However, not every client needs to have a heavy installation of a service mesh. Most clients only work with HTTP, and for them, Traefik is enough for my needs.

I am using the free version, and the best feature is that it is easy to use. Traefik Enterprise brought us an easier way because we faced a problem with Ingress Nginx. In this case, we needed another tool which could replace our current stack. We found Traefik easily and discovered how it is installed. When you have some more specific cases on Ingress, Traefik may not be enough, but in most cases, it is easy to work with it.

I am still exploring Traefik Enterprise and reading the documentation. I need a little bit more expertise on it.

With Traefik, there are a lot of files that should be specified for Traefik. With Nginx, we have one file, which is Ingress Nginx, but with Traefik, there is more than one file you need to configure to work it as well. For example, when you are working with CORS policies or any kind of specific configurations.

It saved a lot of time when we faced replacing Nginx, and it saved maybe weeks of work for our DevOps department.

I have been doing this for over six years. I started my work as a software engineer, and right now I am working as a DevOps engineer.

Traefik is working well. The accuracy and reliability of the output is working fine for me. I do not care about Ingress too much, and Traefik is closing my tasks shortly. I love it.

Traefik in the free version supported all security patches, and it is maintainable. In this case, I feel it is secure, but you need to configure a little more about CORS policies, rate limits, and others by yourself. All about the security patches are coming and working well, so I do not have any issue.

It works well. It is deploying one pod and working as well. I do not have any issue with it. I have B2B clients who have B2C clients, not more than one thousand or two thousand, and it works as well.

I have worked with the service mesh Istio, and it was kind of heavy for clients which do not have true heavy products. In this case, I changed back to Traefik and it works.

I did not switch from Traefik to any others. I tried before service mesh, Gateway API, and Ingress Nginx, but the most reliable for me right now is Traefik.

Traefik Enterprise brought us an easier way because we faced a problem with Ingress Nginx. In this case, we needed another tool which could replace our current stack. We found Traefik easily and discovered how it is installed. When you have some more specific cases on Ingress, Traefik may not be enough, but in most cases, it is easy to work with it.

With AI, I spent maybe twenty minutes on the initial setup.

It saved a lot of time when we faced replacing Nginx, and it saved maybe weeks of work for our DevOps department.

I cannot say clearly because I did not check it.

Because it is easy to use. As I said before, it is easy to replace our current Nginx. We need to add some additional configuration files in some cases, depending on the clients, for CORS policies and others, but it supports the same implementations as Nginx. I love it.

I have worked with the service mesh Istio, and it was kind of heavy for clients which do not have true heavy products. In this case, I changed back to Traefik and it works.

I mean about the configuration. That is all that I know for now. My review rating for Traefik Enterprise is ten out of ten.

Traefik Enterprise serves as an ingress controller for Kubernetes infrastructure and virtual machines.

I appreciate Traefik Enterprise's automatic service discovery feature because it truly helps with deploying containers for our Kubernetes workloads.

The best features Traefik Enterprise offers include automatic service discovery and excellent integration with GitOps. The automatic service discovery helps us with automation, meaning we don't have to perform any manual work when deploying workloads; this goes a long way in making developers and engineers more efficient at their work, allowing them to focus their attention on other tasks. Regarding the GitOps aspect, it integrates very well with Argo CD, but I cannot give more details due to some NDAs.

Traefik Enterprise has positively impacted my organization by making myself and my colleagues more efficient, allowing us to invest more time in other tasks because we are comfortable knowing how Traefik Enterprise operates and the automation we implemented with it.

Traefik Enterprise could improve with support for other products, but it's fairly complete. I don't have any specific improvements to mention because we have everything we need.

I have been using Traefik Enterprise for almost six years.

Traefik Enterprise is stable.

Traefik Enterprise is scalable, and we didn't have any issues with uptime.

Traefik Enterprise's customer support is very good. I would rate the customer support 10 out of 10.

Positive

We previously used Nginx Proxy Manager, but we evaluated Traefik Enterprise and saw that it had more features and was better suited for more customers.

We have seen a return on investment with Traefik Enterprise because we saved time.

Before choosing Traefik Enterprise, we evaluated Nginx Proxy Manager among other options.

My advice for others looking into using Traefik Enterprise is to be patient; although the initial onboarding is somewhat complex depending on the environment, once Traefik Enterprise is set up, it will be easy to manage, and the automation itself is worth it. I have no additional thoughts about Traefik Enterprise. I rate this review 10 out of 10.

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.

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.

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.

I have been using Traefik Enterprise for two and a half years. I am a user of the tool.

It is a stable solution. Stability-wise, I rate the solution a nine out of ten.

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.

My company has used Envoy in the past.

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.

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.

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.

My main use case for Traefik Enterprise is for enterprise applications, security purposes, support, and scalability and reliability.

When I use Traefik Enterprise for security and scalability, I use it for API gateway routing and load balancing microservices on a day-to-day basis.

API gateway routing or load balancing is sufficient for my needs.

The best features Traefik Enterprise offers me involve DevOps, which I find myself using the most.

Traefik Enterprise has impacted my organization positively, especially in the e-commerce sector.

Traefik Enterprise has helped my e-commerce systems by improving routing stability, cost efficiency, reliability, and measurable performance time.

Traefik Enterprise works properly and there is nothing that has been frustrating about it.

Support is available.

My advice to someone considering using Traefik Enterprise is that it is suitable for customers. I would rate this review a 7.