Summary
Highlights
Introduction and Background00:00
The session starts with introductions of the speakers, Nick Gotle and Roman Gershman. Roman provides a background on how Dragonfly was created due to issues faced with Redis at scale during his time with AWS.
Open Source Decision03:15
Roman discusses the decision to open the Dragonfly code on GitHub, emphasizing transparency and building trust with the developer community.
Why Not Fork Redis06:45
Roman explains the decision to build Dragonfly from scratch rather than forking Redis, due to limitations in Redis's design for a multi-threaded paradigm.
Migration from Redis to Dragonfly09:55
The session covers the simplicity of migrating from Redis to Dragonfly, as Dragonfly is a drop-in replacement for Redis with similar APIs.
Dragonfly Architecture13:20
A detailed overview of Dragonfly's architecture is provided, highlighting its multi-threaded design and how it differs from Redis's single-threaded model.
Comparison with Redis Cluster18:10
Roman explains the differences between Dragonfly's multi-threaded architecture and Redis Cluster, focusing on scalability, consistency, and simplicity.
Business Value of Dragonfly21:45
Discussion on the business benefits of Dragonfly, including increased performance, reduced latency, and cost savings.
Current State of the Dragonfly Project24:30
The current status of the Dragonfly project is highlighted, with mentions of community growth, GA status, and features offered by Dragonfly.
Impact of Redis Licensing Change25:50
Discussion on the impact of Redis's licensing change and the subsequent community interest in Dragonfly.
Conclusion and Q&A26:30
The session concludes with a call for audience questions. The speakers thank the audience and provide information on how to explore Dragonfly further.