Kong + Yugabyte: Simplifying App Development in a Distributed World
summary
Kong runs as a lightweight API gateway in front of a Java microservices store app and stores its configuration in Yugabyte as a Postgres‑compatible database, supporting multi‑DC deployments and acting as a TCP load balancer. Live demo shows rate limit 10 requests per 60s; cache drops ~0.36s → 7ms when proxy caching is enabled (memory strategy), proxy port 8000 used, and the portal auto‑publishes Swagger specs. Yugabyte provides row‑level geo‑partitioning and synchronous replication (near zero RPO) and runs on VMs or Kubernetes via Helm/operator.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:50Distributed app challenges
- 3:55Kong for API management
- 6:23Multi-data center Kong
- 7:28Live demo setup
- 8:11Yuga Store walkthrough
- 10:59Register services and routes
- 11:41Rate limiting policies
- 12:45Authentication and security
- 13:28Caching API responses
- 15:57Publishing APIs
- 17:00Developer portal docs
- 18:25Data layer challenges
- 20:48How YugabyteDB addresses data challenges
- 21:51YugabyteDB vs Greenplum
- 22:53YugabyteDB in Kubernetes
- 24:17CI/CD automation
- 25:20Kong API lifecycle
- 26:44OIDC identity management
- 27:27Geo-distribution in YugabyteDB
- 28:53Closing remarks
- 29:14Q&A
related talks
30mImproving a Developer’s Life with Distributed SQL
30mBuilding Cloud Native Applications on Distributed SQL Platform
46mA DB on K8s, Cloud-Native, Open-Source, and PostgreSQL-Compatible: YugabyteDB
30mBuilding Scalable Spring Applications with YugabyteDB
42mAPI Gateway Pattern & Kong in a Microservices World
17mBuilding a Scalable and Performant SaaS Platform with YugabyteDB
30mTechnical Comparison of YugabyteDB with Oracle and PostgreSQL
31mEnd-to-End Stack: Harnessing YugabyteDB & Ecosystem Solutions, Build Apps on Global Scale