API gateway made easy with Ocelot and containers
summary
Shows how to run Ocelot (ASP.NET Core) as a production API gateway using Azure App Service for Containers and Docker, proxying two backends (Customers, Sales) with an ocelot.json config. Builds a custom aggregator that composes customer + sales into one JSON object, adds header transforms to avoid gzip issues, externalizes config via Azure Blob polling, and enforces throttling set to 3 calls per 10s then 30s ban. Demonstration deploys an image to Azure Container Registry and the gateway works end-to-end with staging/production host routing.
AI-written summary · about
chapters (11)
- 0:00Introduction to API gateways
- 6:29Why use Ocelot for API gateways
- 9:20Building API gateway from scratch
- 14:00Routing and versioning with Ocelot
- 18:19View model composition in Ocelot
- 28:17Throttling and traffic management
- 33:04Extending Ocelot with custom features
- 38:54Deploying Ocelot in containers
- 44:52Staging and production environments
- 49:31Platform as a service overview
- 50:18Q&A session
related talks
20mAPI Gateway in a Nutshell
39mMaking Production as Smooth as Development with Azure Spring Apps
59mMake Your Container Apps Smarter With Sidecars and Actions
01h 00mLessons from the API Management Trenches
44mAzure and Containers, the tale of the two inseparable friends
26mAPI Gateway, A Success Story
42mAPI Gateways - The Good, the Bad and the Ugly
17mAddress complicated use cases with NGINX as a Service for Azure