Traefik Hub
Wireless monitoring has improved network performance and currently optimizes coverage and security
What is our primary use case?
My main use case for Traefik Enterprise is in wireless networking, specifically in designing for wireless networking that involves analyzing channel interference, primary signal distance, RSSI, and secondary SNR. I manage trafficking over the network in industrial, stadium, and office areas while designing for coverage and capacity points of view. By installing access points, I connect with networking devices such as routers and switches, configure them, and save the configuration in a DNAC format on the online cloud for Cisco, Aruba, Juniper Mist, and WLC.
What is most valuable?
Traefik Enterprise's best features that I use most frequently are related to WLAN. Traefik Enterprise has impacted my organization by directly improving employee productivity, enhancing network performance, ensuring good channel utilization, and reducing airtime congestion in wireless networking. This applies especially to office areas and manufacturing environments. We have reduced security risks by addressing malware, DDoS attacks, and unauthorized access. In WLAN, bandwidth consumption has been minimized, resulting in good customer experience, as previously we dealt with poor website responses, late transactions, and bad call quality. Infrastructure planning and control have improved, allowing us to update bandwidths, add access points or switches, optimize LAN links, and enhance RF design, which is very beneficial for our business productivity.
What needs improvement?
I would suggest adding more web UI dashboards. Currently, I need to access all network devices through separate logins for different dashboards, so having a single dashboard to log in once and access the complete network would enhance ease of use.
For how long have I used the solution?
I have been familiar with Traefik Enterprise for almost two years.
What do I think about the scalability of the solution?
Handling Traefik Enterprise requires a complete team because one person cannot perform all these tasks.
When I first implemented Traefik Enterprise, the implementation timeline depended on the enterprise's capacity. For example, if you have ten devices in the wireless network, it takes around one to two weeks to set up the complete devices from scratch to finish.
Adoption of Traefik Enterprise has been limited, as only one department, specifically IT and networking, is handling it.
Which solution did I use previously and why did I switch?
Before implementing Traefik Enterprise, I used both manual and automated methods depending on the requirements, but most likely manual methods for tech-related tasks.
How was the initial setup?
The biggest friction point I face with Traefik Enterprise is that a single loophole can impact our entire business significantly. Additionally, interconnecting with the LAN network can affect our global operations because maintaining our network enterprises from one location depends on the performance of that specific network enterprise.
What about the implementation team?
My team did not require formal training on Traefik Enterprise, as they found it intuitive to learn.
What was our ROI?
In terms of numbers, I estimate that for time, with around eight people working, the exact time savings are difficult to quantify. Regarding cost, I can provide a rough estimate of around 1.2 million.
Which other solutions did I evaluate?
While evaluating options besides Traefik Enterprise, I considered tools such as Wireshark, SolarWinds Network Performance Monitor, PRTG Network Monitor, Cisco DNAC, and Ekahau AI Pro. I decided on Traefik Enterprise over the other tools because Wireshark allows us to check packet performance and delivery from network devices to users. SolarWinds Network Performance Monitor allows us to check network health and user experience, and PRTG Network Monitor shows network health. Cisco DNAC enables remote monitoring of access points and wireless access points, while Ekahau AI Pro is an AI software used for wireless site surveys to assess network flow and user experience, helping with predictive design and additional insights.
What other advice do I have?
When I open Traefik Enterprise, my first task is typically to identify network topologies, monitoring tools, correct traffic statistics, assess physical wire or wireless health, analyze traffic flow, and check for bottlenecks. These are the kinds of activities I maintain at the start of the day.
Traefik Enterprise has changed how my team collaborates, as we work transparently together, clearly understanding each other's job roles. As the head of the department, I monitor all activities, assign tasks, and if any issues arise, I delegate work accordingly so my team can continuously operate.
I provided this review a rating of 8.
Routing has improved e-commerce reliability and performance but support experience still needs work
What is our primary use case?
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.
What is most valuable?
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.
What do I think about the stability of the solution?
Traefik Enterprise works properly and there is nothing that has been frustrating about it.
How are customer service and support?
Support is available.
What other advice do I have?
My advice to someone considering using Traefik Enterprise is that it is suitable for customers. I would rate this review a 7.
Automatic discovery and GitOps integration have streamlined Kubernetes and VM ingress management
What is our primary use case?
Traefik Enterprise serves as an ingress controller for Kubernetes infrastructure and virtual machines.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Traefik Enterprise for almost six years.
What do I think about the stability of the solution?
Traefik Enterprise is stable.
What do I think about the scalability of the solution?
Traefik Enterprise is scalable, and we didn't have any issues with uptime.
How are customer service and support?
Traefik Enterprise's customer support is very good. I would rate the customer support 10 out of 10.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
We have seen a return on investment with Traefik Enterprise because we saved time.
Which other solutions did I evaluate?
Before choosing Traefik Enterprise, we evaluated Nginx Proxy Manager among other options.
What other advice do I have?
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.
Single endpoint has simplified microservice routing and has improved traffic monitoring
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with this solution for almost two years in my current field.
What do I think about the stability of the solution?
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.
What other advice do I have?
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.
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.