Sponsored Session: How We Built GLIDE
summary
AWS builds GLIDE as an open source Valkey and Redis OSS 6.2/7.0/7.2 client with a Rust core and thin language wrappers (Python, Java now; Node and Go coming), implementing over 200 commands and finding command coverage takes far longer than expected. Core uses Unix domain socket wrappers or FFI, manages a multiplexed single connections strategy to cut connection counts, and does proactive topology polling (quorum reads from multiple nodes) to avoid reconnect storms; demos show pub/sub resubscribe and scale‑out recovery working with minimal downtime.
AI-written summary · about
chapters (7)
- 0:00Client ecosystem challenges
- 8:24Redis client problems
- 12:19GLIDE architecture
- 16:34Live demo: topology changes
- 25:24Lessons learned
- 28:01Get GLIDE and join
- 29:26Q&A: docs and best practices
related talks
40mSponsored Session: How We Built GLIDE
34mTwo Hard Things: Naming Things & Cache Invalidation, Valkey Edition
10mDave Stokes Talks Open - Episode 8
27mAGL Update
26mAccelerating Innovation With Open Source - "Growing Banyan Trees"
42mFlowDesk and Redis: large-scale cloud deployment of crypto-financial services
33mDiscover Valkey: The Path to Now
22mRedis Alternatives Compared