What is AWS Fargate?
Who uses AWS Fargate?
AWS Fargate Integrations
Why developers like AWS Fargate?
Here are some stack decisions, common use cases and reviews by companies and developers who chose AWS Fargate in their tech stack.
We use AWS Fargate because we want to focus on our business and the value we give to our customers and not on infrastructure management, OS patching and agent updates. Fargate is a way for us to run containers in scale without worrying about the underlying fleet of instances or resource management(bin packing, idle instances. etc)
At Qrvey we moved from a SaaS application running in AWS to a deployed model where we would deploy the complete infrastructure and code to a customer's AWS account. This created a unique challenge as we were Cloud Native and hence were using a lot of AWS Services like Amazon DynamoDB, AWS Fargate , Amazon Elasticsearch Service, etc. We decided to first build AWS CloudFormation templates to convert all our infrastructure into code. Then created a AWS CloudFormation template that would first generate a AWS CodePipeline into a customer's AWS account. This pipeline would then deploy our Infrastructure AWS CloudFormation template and the code on that Infrastructure. This simplified and completely automated our upgrade process as well.
AWS Fargate was a really pivotal decision for us, because it ensured the integrity of code running in production. That was a major requirement for the security and compliance audits (SOC II, etc).
Successfully completing those audits gave us access to new business partnerships, while on the engineering side Fargate reduced the work needed to maintain production apps.
AWS Fargate's Features
- No clusters to manage
- seamless scaling
- integrated with Amazon ECS and EKS