Architecting Business-Driven .NET Microservices in the Cloud
summary
Practical .NET microservice blueprint with code at github.com/trolsmoniio/roio-matchmaking-microservice, claiming scale to 10 million concurrent players using AKS, container images in Azure Container Registry, and a Redis cluster plus Azure Database for PostgreSQL; a back‑of‑envelope estimate predicts about 800 API instances and regional GDNS + load balancers. Architecture separates short API requests from long‑running matchmaking workers, uses domain‑driven design with entities, value objects, domain services (no heavy aggregates), plus Application Insights and Key Vault for observability and secrets.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:31Matchmaking microservice concept
- 8:49Microservices vs monoliths
- 13:29Business requirements for matchmaking
- 16:45DDD fundamentals in microservices
- 21:19DDD strategic patterns
- 25:50Application layer patterns
- 26:11Scaling to 10M users
- 33:55Azure and Kubernetes hosting
- 38:55Summary
related talks
53mPowering 100+ million daily users
32mMicroservices Orchestration with
41m.NET Microservices in Real Life
22mMicroservices Highway to hell
52mI Have a Microservices Architecture and I Didn't Know.
53mHow do we build high‑load microservices
26mImplementing Event-Driven Microservices Architecture (...)
58mMicroservices at Scale - ASP.NET Core, Service Fabric, and Azure in production
