Navigating microservices with .NET Core
summary
Demo deploys a .NET Core app to Kubernetes with Helm manifests, three replicas and a rolling update guarded by readiness probes; backend splits into menu/order/delivery services using gRPC streaming, Redis for queue/pubsub, Zipkin for distributed traces and Prometheus for metrics on port 8080. Benchmarks run constrained configs (down to ~30 MB and 0.25 CPU) and still serve traffic, revealing MVC costs more and that lower-level routing yields higher density.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:10What are microservices
- 1:42The truth about microservices
- 3:52The difference between microservices and backend development
- 6:12Kubernetes
- 16:26Windows vs Mac
- 22:46Demo
- 30:39Distributed Tracing
- 34:57GRPC Push
- 41:27Service Defaults
- 48:57Endpoints
- 50:32Prometheus
- 52:47Prometheus Dashboard
- 54:27Requests and Limits
related talks
01h 07mNavigating microservices with .NET Core
56mResilient Java based microservices with Kubernetes
53mResilient microservices with Kubernetes
40mScaling microservices with Message queues, .NET and Kubernetes
01h 03mCloud Native .NET
53mNext Generation Microservices
49mDeveloping microservices applications on the Kubernetes platform
01h 01mGetting started with Kubernetes for your .NET Application
