TrustRadius: an HG Insights company

AWS Fargate

Score9.3 out of 10

13 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

Top Performing Features

  • Service-level Agreement (SLA) uptime

    The service uptime as a percentage defined in the SLA

    Category average: 8.6

  • Dynamic scaling

    Ease of scaling up or down in response to customer needs

    Category average: 8.2

  • Elastic load balancing

    Automatic balancing and distribution of resources across multiple virtual computers

    Category average: 8.5

Areas for Improvement

  • Operating system support

    Range of operating systems available as pre-configured images

    Category average: 7.9

  • Security controls

    Compliance with security protocols like SSL and AES

    Category average: 8.1

  • Pre-configured templates

    Pre-defined templates for virtual machines

    Category average: 7.6

Containers with snap of your fingers, well almost.

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 !

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