Deploying Micro Frontends to a Kubernetes Cluster
summary
Claims an end-to-end recipe to deploy microfrontends into an AKS cluster using Azure DevOps: a NX monorepo with trunk‑based development, per‑microapp pipelines (and optional Review Apps per PR), Docker/webpack local stitching, and independent deployments to pods behind an Ingress routing /content, /shop, /cart. Architecture uses a federated GraphQL gateway for data, shows routing and state patterns, warns build times grow without caching, and cites a real metric: 9.4 MB homepage download with ~40% unused. AKS + Azure DevOps and per‑app pipelines are shown working end‑to‑end.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:20Critique of monoliths
- 5:26Micro frontend architecture
- 10:41Addressing architectural gaps
- 15:16Monorepo strategies
- 22:36Tooling and NX configuration
- 27:36Trunk-based development
- 32:16Deployment and infrastructure
- 35:15Premium, tradeoffs, and future
related talks
01h 01mDevOps with Azure Kubernetes Service
46mDeliver apps from code to cloud with Azure Kubernetes Service
20mBuilding Microfrontends on AWS
52mBring your ASP.NET Core solutions to Kubernetes in Azure
01h 13mMicrofrontends with React and Kubernetes
24mIndependent deployment of the frontend with Docker and Kubernetes
47mIntegrating Azure AI and Azure Kubernetes Service to build intelligent apps
01h 01mGetting started with Kubernetes for your .NET Application