API Gateway Spring Boot : 1 seule porte pour 6 microservices | System Design en 10 min #2

Six services, six ports. Do you want your mobile app to know all of that? No. You want a single point of entry. That's the role of the API Gateway. Chapters: 00:07 - 6 services, 6 URLs, 6 ports 00:20 - Intro 01:21 - The problem without a Gateway 02:07 - The 5 responsibilities of the Gateway 04:12 - Comparison: Spring Cloud Gateway vs. Kong vs. Nginx vs. AWS 05:45 - ADR #2: Why Spring Cloud Gateway? 06:13 - Implementation: gateway-service module 06:46 - Pitfall: starter-web incompatible with WebFlux 07:04 - Configuring routes in YAML 07:53 - Rate Limiting with Redis 18:40 - Demo: routing + X-Gateway header 21:29 - Demo: 20 OK then 429 Too Many Requests 23:40 - Interview pitfall: single point of failure 24:10 - Recap 24:40 - Outro + teaser Video 3 In this video: The Problem: 6 URLs to know, authentication on each service, CORS everywhere The Gateway's 5 responsibilities: routing, rate limiting, authentication, CORS, aggregation Comparison: Spring Cloud Gateway vs. Kong vs. Nginx vs. AWS API Gateway Why Spring Cloud Gateway for QuickBite (ADR #2)? Pitfall: spring-boot-starter-web is incompatible with Spring Cloud Gateway (WebFlux) Rate Limiting with Redis: token bucket, replenish-rate, burst-capacity Declarative routing in YAML: path-based routing to the 6 services Demo: 20 requests successful, then 429 Too Many Requests In discussion: Is the Gateway a single point of failure? Stack: Java 17 + Spring Boot 3.2 + Spring Cloud Gateway + Redis + Kafka KRaft Source code: https://github.com/Deval123/quickbite “System Design in 10 min” series - Video 2/20 #APIGateway #SpringBoot #Microservices #RateLimiting #Java #Architecture #SystemDesign #SpringCloud 🔥 Subscribe to the channel: https://www.youtube.com/@devalere?sub...