App deployment PaaS battle!
summary
One .NET Core HTTP API gets deployed to Azure App Service, Azure Container Instances, Azure Service Fabric and AWS Elastic Beanstalk using the same codebase and ARM/PowerShell automation, then scored on ramp‑up, IaC, manual and automated deploys, diagnostics, cost, density, scale and frustration. Result: App Insights visibility and App Service wins for speed, diagnostics and density; per-second billing makes Container Instances great for quick tests but limits scale and logs; Service Fabric delivers extreme scale at a five-node minimum and high complexity; Beanstalk is a thin VM wrapper with slower deploys and poor diagnostics; everything runs from a single codebase.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:32PaaS continuum
- 6:50Benefits of PaaS
- 9:18Criteria
- 10:10Development Concerns
- 14:04Vendor Lockin
- 15:24Day to Day Perth
- 16:32App Services from Asia
- 17:01App Service Architecture
- 18:06App Service Plan
- 18:45Visual Studio Demo
- 21:19Scorecard
- 23:41Manual deployments
- 30:09Service Fabric
- 42:24Container instances
- 52:29AWS Beanstalk
- 59:11Wrap up
related talks
52mAzure App Service deep dive
43mTake your .NET apps to the cloud with Azure Q&A
58mAdvanced Azure App Services
36mContinuous Deployment, Testing in Production, Autoscaling and Business Workflows
31mAzure DevOps for System Engineers
53mMicrosoft DevOps on AWS
39mDeploy to the cloud at lightning speed with .NET Aspire and Azure Container Apps
53mHow to Use Docker Containers with Azure Services for Your Solution