The maturity you have in deploying serverless capabilities is crucial. For example, if your process takes less than 15 minutes, then you should consider AWS Lambda or other cloud function services. If your process may take longer than that, then Fargate is the way to go, especially when you are starting to deploy. Your first goal is to provide scalability to your business, particularly to your commercial areas. Once you achieve scalability, you can then focus on cost efficiency. If cost becomes a significant factor as you scale up, you might consider managing a Kubernetes cluster with an auto-scaling service to simplify Kubernetes management. When you need that level of scalability, cloud services like Fargate or even Lambda may not provide the cost efficiency you require. That's my current perspective on this. Overall, I would rate the solution a ten out of ten.
On a scale from one to ten, I would rate it around eight. I would recommend using the product based on the specific workloads they are dealing with. For instance, if they have strict sub-second performance requirements, I might not suggest it. The decision depends on their specific requirements, and I would advise accordingly.
AWS Cloud Architect at a tech services company with 1-10 employees
Real User
Top 20
2022-12-08T17:15:45Z
Dec 8, 2022
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.
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.
A new compute engine that enables you to use containers as a fundamental compute primitive without having to manage the underlying instances. With Fargate, you don’t need to provision, configure, or scale virtual machines in your clusters to run containers. Fargate can be used with Amazon ECS today, with plans to support Amazon Elastic Container Service for Kubernetes (Amazon EKS) in the future.
Fargate has flexible configuration options so you can closely match your application needs and...
The maturity you have in deploying serverless capabilities is crucial. For example, if your process takes less than 15 minutes, then you should consider AWS Lambda or other cloud function services. If your process may take longer than that, then Fargate is the way to go, especially when you are starting to deploy. Your first goal is to provide scalability to your business, particularly to your commercial areas. Once you achieve scalability, you can then focus on cost efficiency. If cost becomes a significant factor as you scale up, you might consider managing a Kubernetes cluster with an auto-scaling service to simplify Kubernetes management. When you need that level of scalability, cloud services like Fargate or even Lambda may not provide the cost efficiency you require. That's my current perspective on this. Overall, I would rate the solution a ten out of ten.
On a scale from one to ten, I would rate it around eight. I would recommend using the product based on the specific workloads they are dealing with. For instance, if they have strict sub-second performance requirements, I might not suggest it. The decision depends on their specific requirements, and I would advise accordingly.
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.
I would rate this solution a seven out of ten.
I rate AWS Fargate an eight out of ten.
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.
Everything in this solution works like a charm. I'd rate it as ten out of ten.