TrustRadius: an HG Insights company

AWS Fargate

Score8.5 out of 10

17 Reviews and Ratings

What is AWS Fargate?

AWS Fargate is a compute engine for Amazon ECS that allows the user to run containers without having to manage servers or clusters. With AWS Fargate there is no need to provision, configure, and scale clusters of virtual machines to run containers.

Categories & Use Cases

AWS Fargate Key Features

Learn about the best (and worst!) features AWS Fargate has to offer, as determined by TrustRadius' reviewers.
Based on 17 ratings of AWS Fargate's features
View all AWS Fargate features

Top Performing Features

  • Dynamic scaling

    Ease of scaling up or down in response to customer needs

    Category average: 8.7

  • Elastic load balancing

    Automatic balancing and distribution of resources across multiple virtual computers

    Category average: 9

  • Service-level Agreement (SLA) uptime

    The service uptime as a percentage defined in the SLA

    Category average: 8.6

Areas for Improvement

  • Pre-defined machine images

    Range of different server configurations available

    Category average: 8.4

  • Operating system support

    Range of operating systems available as pre-configured images

    Category average: 8.4

  • Automation

    Automation of administrative tasks

    Category average: 7.7

Who Buys & Uses AWS Fargate

AWS Fargate Reviews

What users are saying about AWS Fargate.
View all AWS Fargate reviews

A gate to first container deployment Fargate.

Incentivized
Verified User
Team Lead in Engineering (501-1000 employees)

Use Cases and Deployment Scope

We use Fargate to host containerized applications. Our biggest use case is our live-ops management application. The compute behind it comes from Fargate, while other services handle the database, cache, load balancing, and routing. The product supports deploying stateless applications that our internal tools and testing team rely on.

Pros

  • Automatically scales with traffic.
  • You pay only for the CPU and memory used.
  • Runs containers without managing servers.

Cons

  • Offers less control over the underlying server.
  • Storage options are more limited than EC2.
  • Large numbers of tasks may hit launch-rate limits.

Return on Investment

  • Has made seasonal apps/tools cheap to run/maintain.
  • Pay for what you use helps compare many A/B tests.
  • No server management means faster deploys.

Usability

Alternatives Considered

Render, Google Cloud Run and DigitalOcean

Other Software Used

Render, Amazon Redshift, Amazon Virtual Private Cloud (VPC)

Containers with snap of your fingers, well almost.

Incentivized
Verified User
Manager in Information Technology (11-50 employees)

Use Cases and Deployment Scope

easily and quickly deploying serverless compute application without needing to manage servers

Pros

  • scalability
  • ease of use
  • agility to up or downsize

Cons

  • can't think of any

Return on Investment

  • easier to optimize our computer costs
  • transition from server to serverless was easier once we decided to adopt Fargate

Usability

Alternatives Considered

Amazon Elastic Container Service (Amazon ECS)

Other Software Used

AWS Step Functions, AWS Lambda, Datadog, GitKraken, PhpStorm, MySQL Workbench

Fargate Rocks !

Incentivized
Verified User
Engineer in Information Technology (10,001+ employees)

Use Cases and Deployment Scope

In our company, we have been using Fargate a lot since the day it was made publicly available by AWS. This is due to the fact that we deploy every thing using Docker containers. ECS an EKS are good for this, but they are quite complicated to manage, and need a lot of low level maintenance to keep the servers up to date. Fargate on the other hand allow us to not worry about infrastructure. We only need to store the docker image somewhere (Docker hub or ECR), and Ship it to Fargate. Everything related to infrastructure is managed by AWS.

Pros

  • Managed Docker deployents
  • Very easy to scale up
  • Very good integration with EFS and ALBs

Cons

  • Debugging inside a container is quite tricky, but feasable
  • Sometimes it feels a bit opaque
  • Task definitions are still a hassle to create & update

Return on Investment

  • Much less effort is spent maintaining infrastructure
  • Time to market is much shorter once a reusable stack is terraformed
  • Quicker and easier deployments

Usability