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.