That’s a behavior you can achieve with ECS and Fargate by configuring scaling policies as well. Of course, App Runner scales down the number of containers as well. In case the application receives more than 100 concurrent requests per running container, App Runner will scale out by launching a container. App Runner shines in this application area because it allows scaling down to 0.Īpp Runner monitors the number of concurrent requests. Although, there are a lot of applications out there with low traffic by a manageable number of users. Our industry often overemphasizes web-scale applications. So, the simplicity of App Runner limits the possible use cases. You cannot achieve that with App Runner but with ECS and Fargate. For example, your application needs to generate a weekly report for thousands of customers based on a complex database query. The strong focus creates a simple solution, somewhat atypical for AWS.ĮCS and Fargate support a wide variety of scenarios. ScenariosĪpp Runner focuses on a single scenario: a web application answering incoming HTTP requests synchronously. How is that possible? Where does the simplicity of App Runner come from? This certainly does not cover all but the majority of today’s use cases. Instead, App Runner provides an abstraction designed for developers looking for a way to deploy their web application with ease. I want to highlight that App Runner is not a tool that creates and manages all the resources needed for ECS + Fargate in the background. Here is a comparison of the AWS resources needed to host a web application with ECS + Fargate or App Runner. I want to make the difference even more apparent. The following figure shows the networking configuration, a load balancer, as well as different parts of the ECS service.Ĭompare that with the resources you need to configure to deploy a web application on App Runner, illustrated in the following figure. This is a typical architecture for a web application running on ECS and Fargate.
But then, I discovered App Runner, which adds another layer of abstraction and lifts the developer experience to a new level. Deploying a web application with ECS and Fargate felt quite simple to me. So I got very excited when AWS announced Fargate, a managed compute layer for ECS. Maintaining and scaling the needed EC2 instances was wasting a lot of my time. What’s the simplest way to run containers on AWS? My first relevant container workload was running on a fleet of EC2 instances managed by ECS.
0 kommentar(er)
