Single Entry Point or Single Point of Failure: The Path to a Non-blocking API Gateway
summary
A walkthrough of choosing and evolving an API Gateway for Java microservices, comparing current market options and open-source tools. The talk demonstrates a real-world migration from Nginx + monolith to Spring Boot + Netflix Zuul + microservices, then to reactive Spring Cloud Gateway, showing live code: building a Zuul-based gateway with servlet-stack filters, measuring blocking-API performance issues, rewriting to Spring Cloud Gateway with equivalent features, writing non-servlet filters, and adding Resilience4J circuit breaker. Technologies: Java, Spring Boot, Spring Cloud, Zuul, Spring Cloud Gateway, Resilience4J.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:04What is entry point
- 3:14API Gateway pattern
- 6:26Zuul classic approach
- 7:34Zuul operation
- 9:19Blocking approach problems
- 15:29Discovery and load balancing
- 16:56Demo environment
- 22:20Zuul failure cause
- 24:48Zuul problem solutions
- 25:11Non-blocking approach
- 27:20Switch to Spring Cloud Gateway
- 28:47Filters in Spring Cloud Gateway
- 33:26Demo of Spring Cloud Gateway
- 36:44Throttling solution
- 41:16Circuit Breaker usage
- 44:03Spring Boot 3 advantages
- 45:50Zuul drawbacks vs Gateway benefits
- 47:13Summary
- 48:16Q&A
related talks
51mIntroducing Spring Cloud Gateway
51mThe API Gateway is dead! Long live the API Gateway!
27mMaster API Gateways: Boost Your Microservices Strategy
01h 00mModern API Versioning and Enterprise Ready AI Enablement with Spring Cloud Gateway
20mAPI Gateway in a Nutshell
19mMastering Multi-API Gateways: Strategies for Scale, Security & Success.
42mAPI Gateways - The Good, the Bad and the Ugly
48mTransforming a monolith to an API platform