Containerized Deployments for your SPA and API
summary
Uses Vue CLI and dotnet CLI to build a simple weather-forecast SPA and API, then creates multi-stage Dockerfiles (Node+nginx for the front end, ASP.NET runtime for the API) and demonstrates three deployment patterns: one container one domain (works, but forces joint scaling), two containers two domains (works with CORS and baked-in env vars), and two containers one domain behind a Kubernetes Ingress (works and allows independent scaling). Live examples run successfully locally.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:41SPA and API separation
- 4:10Dev setup: webpack and proxy
- 7:16Hosting strategies for containers
- 9:29Single container on one domain
- 13:24Single-container pros and cons
- 15:11Two containers on two domains
- 16:32Configuring CORS headers and environment variables
- 19:46Scaling and env-specific builds
- 20:51Two containers on one domain with Kubernetes
- 23:23Kubernetes ingress config
- 26:36When to use two containers on one domain
- 27:17Server-rendered SPA considerations
- 28:40Monolith vs microservices
- 29:45Deployment strategies summary
- 30:28Q&A
related talks
48mContainerized Deployments for your SPA and API
58mMulti-container applications with .NET Core on Kubernetes
52mBring your ASP.NET Core solutions to Kubernetes in Azure
35mBuilding Apps with Containers, Functions and Managed Services
01h 15mContainerize .NET Apps and deploy to Kubernetes
54mDeploy Angular and Node to the Cloud
01h 03mScaling Docker Containers using Kubernetes and Azure Container Service
35mDeploying Your Angular Apps
