Reference Architecture for Running Modern APIs w/ NGINX Unit & Web Server
summary
Shows a concrete reference architecture: runtime uses NGINX Unit (dynamic JSON config over a unix socket, polyglot support for eight languages) to host three Node.js Express APIs in Docker, pushed to AWS ECR and pulled on an EC2 instance; gateway uses NGINX web server with TLS, nested locations, upstream blocks and proxy_pass. Demos update an events API live and deploy successfully. Includes rate limiting at 2 req/s, basic auth via htpasswd, and the docker entrypoint.d pattern for startup and config.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:21What we're going to build
- 5:30Introducing NGINX
- 8:14What is NGINX Unit
- 18:15Process overview
- 19:44Installing NGINX Unit (simple)
- 22:20Unit configuration
- 25:37Unit routes 2
- 47:07Installing NGINX (official)
- 47:31Installing NGINX (simple)
- 48:19NGINX Open Source Cycle
- 55:13Define our API gateway
- 58:43Define JSON error responses
related talks
01h 03mNginx for .NET Developers
21mThe Future of the Dynamic Application Server
42mKilling the Reverse Proxy from the Inside: the Evolution of NGINX...
54mNGINX beyond nginx: njs, nginMesh, Unit...
01mUnit
01h 06mSo many Docker platforms, so little time...
35mEvolving your APIs, a step-by-step approach
31mContainerized Deployments for your SPA and API
