Let me handle that for you... Why you need a reverse proxy in your architecture
summary
Explains why a single public reverse proxy reduces attack surface and moves SSL, compression, routing, health checks and caching out of app code, with live demos using nginx caching (serves a 20,000‑digit PI result from cache after app shutdown) and Traefik auto-discovery (Docker labels/Kubernetes ingress, middleware redirects, LetsEncrypt certs). Shows load‑balancing across three replicas, WebSocket passthrough, and the tradeoff: nginx provides response caching today while Traefik provides dynamic container-native config and built‑in certificate automation.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:41What is a reverse proxy
- 3:07Reverse proxy features
- 9:07Demo: Caching with nginx
- 16:33Demo: Multiple sites with nginx
- 21:13Demo: SSL with nginx
- 26:34Traefik vs nginx
- 30:05Demo: Traefik in Docker Swarm
- 36:46Demo: Traefik in Kubernetes
- 39:35Benefits of reverse proxies
- 42:21Advanced patterns
- 44:04Resources and closing
related talks
31mIntroduction to Traefik
31m"This Website is Not Secured" You Had One Job, Configuring the Edge Proxy!
52mTraefik, a modern reverse-proxy
17mAddress complicated use cases with NGINX as a Service for Azure
39mHow to Reconcile Security and Agility for the Good of Your Applications
40mDeep Dive Into Traefik 3.0
37mThe Zero Trust Odyssey: Our Journey to Modernize Internal Access
33mBuilding a Secure, Multi-Protocol and Multi-Tenant Cluster for Internet-Facing Services [A]