Architecture overview
It’s common for enterprise .NET applications built in the last
decade to follow a layered
n-tier
This guide uses the familiar
MvcMusicStore
Many customers start their cloud journey with a lift-and-shift
approach, running their n-tier .NET Framework applications on EC2
without any code changes. It’s common for these deployments to have
more than one EC2 Windows instance with an
Application Load Balancer
Along with the Application Load Balancer, developers can use
AWS Auto Scaling
In this guide, you replatform this traditional n-tier .NET Framework
application to run on Amazon ECS using
AWS App2Container
Amazon ECS runs natively with AWS services such as Application Load Balancer and Auto Scaling, allowing developers to start with the minimum amount of compute to meet user requirements and scale dynamically as the incoming traffic increases. The high-level architecture for the containerized version of this application follows, and is the target of the transformation detailed in this guide. In the following diagram, the 1 vCPU, 2 GB blocks represent the Amazon ECS tasks where the application containers run.
Additional benefits of moving to containers are realized when teams also implement automation and DevOps. A cloud-optimized, containerized application allows you to quickly and frequently deliver consistent applications to your users. A common development pipeline for nearly continuous deployment with AWS follows.
Now that you have an idea of the before and after state of the application that you will modernize in this guide, walk through the procedural guidance to complete this transformation quickly and safely.