Deciding where to host .NET applications on AWS
Microsoft Workloads on AWS Blog
This article discusses different compute options on AWS for hosting .NET applications, covering web applications/APIs, background services (batch jobs and background processors), and their respective tradeoffs.
Specifically, the article covers:
- Compute services on AWS: EC2 instances, containers (ECS, EKS, Fargate), and serverless (Lambda)
- Web applications and APIs: Fast response times, unpredictable load, high availability; Options - serverless (Lambda), containers (ECS, EKS + Fargate), EC2
- Background services: Batch jobs vs. background processors; Options - EC2, containers, serverless (Lambda, Step Functions)
- Conclusion: Consider application characteristics and factors like operations, performance, and cost to choose the right compute service
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.