Building a JVM-Based Cloud Native API Gateway
summary
Mercedes‑Benz.io builds a JVM cloud‑native API gateway (Frontend Facing Gateway) using Kotlin, Spring Cloud Gateway and Spring Boot with Quarkus native operators and MongoDB; routes are stored as a GatewayService CRD and mapped to Spring routes via MongoDB change streams for instant route reloads and custom Spring Cloud Gateway filters. A per‑cluster Kubernetes Operator (Java Operator SDK + Quarkus native) reconciles manifests to the management API, cleaning up ghost routes; production handles 1,000–2,000 req/s across 40 teams and works in production.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker intro
- 1:26Who we are at Mercedes-Benz IO
- 2:08Why we needed an API Gateway
- 5:46Objectives for the API Gateway
- 6:30First iteration of the solution
- 8:15API Gateway implementation details
- 10:28Live demo of route management
- 17:34Limitations of the first approach
- 19:01Introducing the Kubernetes operator
- 21:07Custom resource definition explained
- 24:00Operator reconciliation process
- 28:36Live demo of Kubernetes operator
- 31:56Handling errors in reconciliation
- 35:58Advantages of the new approach
- 40:57Implementation simplicity and extensibility
- 41:42Current usage and scale of the gateway
- 42:10Q&A session
related talks
31mServerless Java in Action: Cloud Agnostic Design Patterns and Tips
36mCrafting Intelligent Cloud Native applications with Quarkus
55mKogito - Business automation powered by cloud native Java
42mNative Cloud Native with Java, Quarkus and MicroProfile
53mMeet Quarkus
32mCloud-era Integration with Camel Quarkus
40mCloud Native Java
49mKubernetes. From 0 to Production-Grade with Java