Clean up this mess - API Gateway (...)
summary
Shows how to organize a .NET microservices application using an API Gateway (to route and distribute requests among services) and Service Discovery (a registry where microservices publish their availability or outages). Covers practical use of these two mechanisms to manage growing projects and improve service management.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:31Project problems and service split
- 6:01API Gateway need in microservices
- 9:16What is API Gateway and its benefits
- 11:24API Gateway with Ocelot implementation
- 16:23Service Discovery need
- 18:57Service Discovery tools comparison
- 20:23Consul configuration and operation
- 25:44Registering services in Consul
- 28:13Load balancing with FabIO
- 31:04FabIO vs client usage
- 32:34Summary of benefits and challenges
- 34:38Recommended sources
- 35:40Q&A
related talks
27mMaster API Gateways: Boost Your Microservices Strategy
29mImpact of Microservices Architecture on API Management
01h 05mAPIs and Microservices in ASP.NET Core Today and Tomorrow
46mCloud based API gateway or more?
30mOptimizing Microservices with Kong API Gateway: Simplified Management and Improved Security
26mBuilding Scalable Microservice APIs From The Beginning
26mAPI-Driven Microservice Architecture: Empowering Digital Transformation
29mThe API Gateway Maturity Matrix: Where Do You Rank?