How xpertsoftorg/xaf-blazor-kubernetes-example works
Project type and purpose
• This is a full-stack, containerized Blazor Server application (XAFContainerExample) with an EF Core/XPO module, deployed to Kubernetes (AKS/K3s) alongside a SQL Server database. Its purpose is to demonstrate horizontal scaling (HPA), ingress routing, and persistent storage in Kubernetes.
File structure
• Top-level solution (XAFContainerExample.sln) contains two projects:
• XAFContainerExample.Blazor.Server (ASP.NET Core Blazor Server host + Controllers, Services, Pages, wwwroot, Startup/Program)
• XAFContainerExample.Module (BusinessObjects, DbContext, Reports, Module.cs)
• Deployment/configuration artifacts:
• Dockerfiles (Linux, Windows, Nginx)
• docker-compose.yml (+ nginx variant)
• K8S folder with manifests: PersistentVolumeClaim, MS SQL Deployment & Service, App Deployment & Service, Ingress, HPA
Core components
a. Client Tier
• Web browsers/users (simulate concurrent connections)
b. Ingress & Networking
• NGINX Ingress Controller (as a Kubernetes Ingress resource or Docker Nginx container)
• LoadBalancer / Kubernetes Service(Type=LoadBalancer)
• Ingress rules (TLS/non-TLS, sticky sessions for Blazor Server)
c. Application Tier
• Kubernetes Deployment “app-depl”
• ReplicaSet & Pods running XAFContainerExample.Blazor.Server.dll
• HorizontalPodAutoscaler adjusting replicas (minReplicas=1, maxReplicas=20, CPU target=50%)
d. Data Tier
• Kubernetes Deployment “mssql-depl” for Microsoft SQL Server
• ClusterIP Service for SQL Server
• PersistentVolumeClaim → PersistentVolume backing SQL data
e. Optional Docker Compose scenario
• Two containers: “web” (Blazor Server) + “db” (mssql/server), Docker network
• Optional “nginx” reverse proxy
Relationships & data flows
• Monitoring/Scaling: HPA watches CPU metrics of Deployment → adjusts Pod count
• Kubernetes control plane orchestrates Deployments, ReplicaSets, Services, PVCs, Ingress
Architectural patterns & design principles
• Modular monolith: UI (Blazor Server) & business logic in separate assemblies (Server vs Module)
• Containerization: separate images for Linux/Windows hosting + sidecar Nginx reverse proxy
• Infrastructure as Code: Kubernetes manifests define desired state (Deployments, Services, Ingress, HPA, PVC)
• Horizontal scaling via HPA based on CPU utilization
• Sticky sessions for SignalR WebSockets in Blazor Server
Detail level
• Module project as a component inside the Blazor Server Pod
• If desired, overlay Kubernetes namespace segmentation