AWS Fargate Reviews

I like their containerization service. You can use Docker or something similar and deploy quickly without the know-how related to, for example, Kubernetes. If you use AKS or Kubernetes, then you have to have the know-how. But for Fargate, you don't need to have the know-how there. You just deploy the container or the image, and then you have the container, and you can use it as AWS takes care of the rest. This makes it easier for those getting started or if you don't have a strong DevOps team inside your organization. 

I heard from my team that it's not easy to predict the cost. That is the only issue we have with AWS Fargate, but I think that's acceptable. AWS Fargate isn't user-friendly. Anything related to Software as a Service or microservice architecture is not easy to implement. You're required to have DevOps from your side to implement the solution. AWS Fargate is just a temporary solution for us. When we grow to a certain level, we may use AKS for better control.

I have been using AWS Fargate for around three years.

AWS Fargate is a stable solution.

I think AWS is the top tier right now, and I have no concern about scalability. If there is any issue related to scalability, I believe it's just a problem with our DevOps team's ability or architecture. Because, for example, Twitter or Netflix use AWS service, and there's no hassle there.

We also use Azure because Azure is our preferred repository for internal services. We use Azure for internal customers, and for external customers, we use AWS.

I think the initial setup was straightforward. For the DevOps part, you just need one person. But because it's an ongoing product, we have more than ten developers taking care of it.

Our in-house team implemented this solution. 

What's suitable for potential users depends on their company's IT capability. For a small company, it's best to engage a consultant service for help. For example, we could consult others on the solution in my previous outsourcing company. It wouldn't have been a very good one if we did it ourselves. My current company is very big, and we have the know-how here, and it's easier for us to make the decision.

On a scale from one to ten, I would give AWS Fargate an eight.

AWS Fargate is a container-based application. I have experience with AWS Fargate for a Webex-like application similar to YouTube. One of their applications was monolithic, and the challenge was to migrate it to a container-based architecture. The customer wanted to use AWS Fargate. However, the main challenge was dealing with a Docker-type application where multiple containers needed to be created in a firewalled environment. I worked with Amazon to create a solution using a single Fargate task definition to deploy a multi-container setup successfully.

AWS Fargate is an easy-to-use tool to simplify setup. You only pay for the resources you use. If you need to quickly create, delete, or scale applications without managing resources like EC2 instances, Fargate is the best service to use.

AWS needs to work on multi-container enterprise developer components. They need to simplify that kind of setup.

I have been using AWS Fargate for over a year.

The product is stable. It is not recommended  for a large-scale traffic application. Fargate can be used in any application with less traffic.

If you have the premium support, then it's very good.

Compared to EKS, using AWS Fargate is simpler and more efficient for developers. With EKS, developers need to manage and configure the Kubernetes cluster, which can be complex. In contrast, Fargate handles the infrastructure management, allowing developers to focus on their applications. It's more like a straightforward, automated setup.

Setting up AWS Fargate to use private data is straightforward. You need an ECS container stored in Amazon ECR. From ECR, you can create a task definition and a service. Within a few minutes, you can have the application up and running.

The tool is suitable for testing. You have to pay for AWS  only.

AWS Fargate can be used to run almost any type of application. It requires an application container, such as an application server container, a backend container for a database like MySQL, and a frontend container, which could be a web server like Apache. Multiple containers must be deployed simultaneously, and configuring these multiple containers within a single cluster can be somewhat complex.

I recommend the tool for the initial event; you can try it out. If you feel it's reliable, you can consider adding it on. However, if you feel that it will mainly depend on your current application, you may need to evaluate it further. It is easy to learn.

Overall, I rate the solution an eight out of ten.

AWS Fargate is a managed container that you can put some code into and have it just run. You can have a full website or code that calculates something. It is a building block for a whole infrastructure.

This service could be improved if the AWS Console was either reverted to an old version or if it updates its functionalities. I would like to see the older dashboard instead of the newer version. I don't like the new dashboard. 

I have been using AWS Fargate for more than a year. 

I am very happy with the stability of this solution.

I would rate the scalability of this solution a ten. At the moment, I believe there are three people working with the AWS Fargate solution in our organization.

I was never in contact with their technical support team.

The initial setup was fairly easy. I am coding it and I am doing it as an infrastructure service. I am using CDK to deploy it. If you have it in code, it's fairly quick.

AWS Fargate is worth the money and organizations do see a return on investment with it. 

I would advise others that before they use this solution, they figure out what they want to achieve. There are many solutions available and you should use the most appropriate one. The main concept is, to use the most managed service you can get because that's the point of the cloud. So, try Lambda. If you can't do Lambda, use Fargate. If you can't Fargate, then use ECS. If you can't do ECS, then you can use ROSA or Kubernetes, or something like that. But if you end up with a virtual machine, then question yourself, "Why are you in the cloud in the first place?"

This solution costs a bit more than ECS, but it's not terrible. It's four times less than ROSA, so it's good. It costs more than Lambda. So, if you have to use it and you can't use Lambda, then use Fargate. That's the concept.

I think AWS Fargate is worth its money.

In terms of process documentation and speed, it really depends on what how many CPUs and memory you put in and whether you get adequate speed. For me, it's more than enough. All those functions are primitive functions. They mostly don't need big CPUs and stuff. You just break stuff into many microservices.

AWS Fargate has many valuable services. It does the job with minimal trouble. It's very observable. You can see what's going on and you have logs. You have everything. You can troubleshoot it. It's affordable and it's flexible.

I would rate AWS Fargate a ten.

The most valuable feature is the complete independence of doing administrative courses for your deployment. You don't have to touch them or do fine-tuning to create more scale out or scale in. If you create your deployment with a good set of rules for how to scale in, you can just set it and forget it.

The main area for improvement is the cost, which could be lowered to be more competitive with other major cloud providers. Because eventually, the cost of the infrastructure gets higher, which means clients opt for fewer deployments in order to cut costs.

I've been using this solution for two and a half years.

Everything in this solution works like a charm. I'd rate it as ten out of ten.