Unable to understand AWS Fargate Pricing

Viewed 50

We have a requirement of deploying Redis as an External Load Balancer Service on AWS-EKS (Elastic Kubernetes Service). As Redis will be a statefulset which of the following combination will be the best fit with EKS -

  • EKS with Self-managed nodes
  • EKS with Managed Node Groups
  • EKS with AWS Fargate

Although, I have studied that AWS Fargate should be used for deploying stateless applications.

Fargate, thus far, has been ideal for running stateless containerized workloads in a secure and cost-effective manner. Secure because Fargate runs each pod in a VM-isolated environment and patches nodes automatically. Cost-effective because, in Fargate, you only pay for the compute resources you have configured for your pod.

I didn't understand how stateless applications will be cost-effective. Kindly verify the below statement. It would be quite helpful.

In the stateless applications, the container will be in the running state, when there will be requests and otherwise no. of instances will be 0 just as in GCP Cloud Run. Whereas in the stateful ones, the container will be running every time. And for this reason, we should use, EC2 instances for stateful applications

0 Answers
Related