Introducing Spring Cloud Gateway and API Hub for VMware Tanzu
summary
Spring Cloud Gateway for VMware Tanzu ships as a CF marketplace service that deploys on-demand gateway apps via a service broker, supports HA by setting count>1, and manages routes via JSON or a routes REST API. It enforces SSO (SAML/OIDC) with token relay into backend headers, supports mutual TLS with XFCC header checks, and implements cluster-synchronized rate limiting without Redis using an in-memory grid and a leaky‑bucket greedy replenishment (e.g. 100/sec ≈ 1 every 10ms). API Hub aggregates gateways via OpenAPI aggregation and offers no external Redis key management and try‑out UX; demo (Animal Rescue) works end-to-end.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:26VMware Tanzu Application Service (TAS)
- 3:44Best of Spring Open Source with VMware Tanzu Integration
- 5:25Function of an API Gateway
- 7:59What is a Route?
- 9:00Let's Create a Gateway
- 12:10Service Bindings
- 13:14Container to Container Networking
- 17:40Spring Cloud Gateway Predicates
- 19:58Filters allow you to do things with request/response
- 21:07Single Sign-On
- 26:05Token Relay
- 27:40End-to-end mTLS
- 30:53Client Certificate validation
- 31:38Rate Limiting
- 33:47High Availability Using the count parameter you can horizontally scale your Gateway to a given number of instances
- 34:58Host and Domain
- 36:10Cross Origin Resource Sharing (CORS) Configuration
- 40:12API Hub - how it works
related talks
51mIntroducing Spring Cloud Gateway
53mSpring Cloud Gateway Recipes
47mSpring Cloud Gateway: Resilience, Security, and Observability
43mSpring Cloud Gateway: Resilience and Security
51mThe API Gateway is dead! Long live the API Gateway!
01h 00mModern API Versioning and Enterprise Ready AI Enablement with Spring Cloud Gateway
48mDynamic OpenAPIs with Spring Cloud Gateway
51mSingle Entry Point or Single Point of Failure: The Path to a Non-blocking API Gateway