Nginx for .NET Developers
summary
A .NET Core Web API runs in Docker with Kestrel on port 5000 and is put behind Nginx reverse proxy on port 8080, adding compression, security headers and disk caching via proxy_cache_path. The config shows proxy_cache_valid, proxy_cache_lock and background update so first request fills cache, later requests return hits; demo toggles miss→hit. Docker Compose scales the web service to three instances and Nginx load balances (round‑robin). SSL and health checks are mentioned but not demonstrated.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:02Who am I
- 2:20Where I work
- 3:16Agenda
- 5:59Framework
- 6:43Docker
- 9:13Request
- 10:12Why Nginx
- 11:25Building Nginx
- 13:46Running Nginx again
- 14:55Kestrel
- 18:13Performance
- 19:17What is Nginx
- 21:18IIS vs Nginx
- 26:30Nginx Diagram
- 27:50Nginx Configuration
- 36:04Reverse Proxy Shutdown
- 43:44HTTP Cache
- 50:04HTTP Cache Demo
- 53:49Upstream
related talks
49mNginx as reverse proxy for your (micro) services (...)
01h 30mReference Architecture for Running Modern APIs w/ NGINX Unit & Web Server
53mDocker: What Every Angular Developer Should Know About It!
42mKilling the Reverse Proxy from the Inside: the Evolution of NGINX...
22mRapidly Developing Microservices with Node js and Docker
01h 18mEmbracing Docker simplicity - while harnessing platform power
48mContainerized Deployments for your SPA and API
49mTaking your .NET Core container solution from laptop to production