This post explores the API gateway pattern using Spring Cloud Gateway and Netflix Zuul, highlighting their use cases, benefits, and drawbacks. It delves into the transition from monolithic to microservice architecture, the role of API gateways in client request routing, and the advantages of a non-blocking API gateway. The post also explains filter implementation, service discovery mechanisms, and performance under load conditions. Additionally, it discusses the pros and cons of both gateways, emphasizing the flexibility and modern features of Spring Cloud Gateway.
Table of contents
Spring Cloud Gateway: The Single Point of Entry or Failure — a Path to Non-Blocking API GatewayIntroductionWhat is API gatewayWhat is servlet context?How to organize filtersFilter run order (@Order)Service DiscoverySetup descriptionNetflix ZuulWhy did the gateway fail?How a non-blocking API gateway works: an example on Spring Cloud GatewayReactive gateway and blocking APIs: is it legal after all?Spring Cloud GatewayGlobal FiltersRouting FiltersRouting Filters with a configurationBuilt-in filtersSpring Boot 3: native image support out of the boxPros and cons of ZuulPros and cons of Spring Cloud GatewayWhat we’re having by the endSort: