What is our primary use case?
Our client is doing some image analysis, and we need a robust system that won't go down during the image rotation, so we are using Amazon EKS. With this solution, our services will not go down during their work, and data will remain safe and available to the user.
What is most valuable?
Firstly, whenever a service goes down, EKS automatically makes up that part, enabling the services to remain available. And secondly, whenever we deploy anything, we don't have to consider security between services because EKS provides that as well. We need to configure some supportive plug-ins and tools, which is relatively easy. This feature also provides monitoring, so if our service goes down, we have an alert mechanism and logging.
We can deploy EKS microservices on any service we are developing.
What needs improvement?
The solution could be improved by adding monitoring, filtering, and logging capabilities to its current CloudWatch features.
For how long have I used the solution?
We've been using the solution for one and a half years.
What do I think about the stability of the solution?
We haven't faced any major issues in one and a half years of use. We had an issue with storage, which we capped, giving us access to more space from the cloud. There are some other minor issues, but nothing major.
I would rate the solution's stability as eight out of 10.
What do I think about the scalability of the solution?
We use the solution because it allows you to scale your application up and down.
We have 500 data scientists actively using our EKS tool at any time.
How are customer service and support?
We usually get support on time, but sometimes we have critical issues or something they need more time to deal with.
We would give them nine out of 10 for the quality of support.
How was the initial setup?
The initial setup is straightforward.
What about the implementation team?
When deploying the solution, we used Jenkins to develop a CI/CD pipeline. It was a one-person job that took about 20 to 25 minutes.
What other advice do I have?
On a scale of one to 10, we would give the product an overall rating of eight.
EKS is for deploying microservice projects. If you have multiple services in your application, you can deploy them and design your application accordingly.
We can deploy EKS microservices on any service we are developing.
I would certainly recommend the product to new users, but it would depend on the technology stack and the project. If a certain use case requires EKS, I would definitely advise using EKS rather than Google or Azure's EKS. I recommend Amazon Cloud Services for its reliable support and minimum downtime.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.