Envoy & Service Mesh for Databases: What the Future Holds
summary
Envoy parses the Postgres wire protocol via a Postgres filter and a tcp proxy, routes connections to a four-node Yugabyte cluster (listener on port 1968) and emits per-message stats and metadata that can be used for access control, routing and outlier detection. A demo using getenvoy bootstrap and round‑robin upstreams shows Envoy logs every frontend/backend message, reporting ~2,500–10,000 messages and ~773 inserts during a run. TLS to the database and query-based routing are under active development but the proxyed setup works end to end.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:29Vhy Envoy: Direct & Indirect Dependencies of an Application
- 11:52How do I get started with Envoy?
- 12:46ervice Mesh: to manage a Fleet of Envoys
- 18:06Multiple Mesh with Tetrate Service Bridge (TSB)
- 21:55Envoy Terminologies & internals: path of data
- 25:26nvoy Runtime Config
- 33:34ugabyte DB: Distributed SQL with PostgreSQL compatibility
- 34:35ugabyte DB: Deployment Options
- 46:39Brainstorming potential future state
- 57:48How do I follow the communities?
related talks
30mPostgreSQL Network Filter for EnvoyProxy
29mEvolution of Envoy as a Dynamic Redis Proxy
53mThe Future of Observability in Postgres
23mPostgres as a Message Broker
51mJump Start Your Developer Journey in 60 Minutes: Go from 0 to Expert
49mUnified Observability: Monitoring Postgres Anywhere with OpenTelemetry
50mThe Immortal Postgres Web
51mEmbrace, Extend, Evolve - Making PostgreSQL Work for a Cloud Native World