RedisConf17 - Redis Development, An Update - @antirez
Download as PPTX, PDF0 likes609 views
Redis 4.0 will include several major new features and improvements including PSYNC2 for better replication, UNLINK for non-blocking DEL operations, and modules to allow building additional functionality on Redis. Streams will be a new data type in Redis 4.2, providing an abstract log file structure for ordered, timestamped entries that allows for efficient random access, deletion of old data, and multiple consumers similar to Kafka. Streams are designed to address use cases like time series data and message queues more efficiently than existing Redis data types.
RedisConf17 - Redis Development, An Update - @antirez
- 1. Redis development: an update @antirez
- 2. Redis 4.0
- 3. MORE HACKING
- 4. More hacking • PSYNC2 bug (Alibaba + Amazon + Redis Labs <3) • RDB modules values • Modules thread-safe contexts
- 5. 4.0 big ones
- 6. PSYNC2 Better replication for Redis
- 8. MODULES Redis as a framework to build things
- 9. THREADED CONTEXTS Non blocking O(N) operations
- 10. LRU + LFU Better eviction = better caches
- 11. RDB + AOF Makes AOF more viable for most
- 12. MORE Defrag, Redis Cluster improvements, …
- 13. ETA RC now, GA in a few weeks
- 14. 4.2 preview
- 15. 1. Streams More threading Better cluster Client side caching
- 16. DISQUE A showcase for Cluster modules
- 17. Why streams?
- 18. Use case driven process • Time series (+ random access) • Multiple consumers problem
- 19. Sorted sets • Optimized to *move* elements around • They are sets: unique elements • Wasteful if not used for the right task
- 20. Pub - Sub • Not a data structure :-) • Fire and forget • Adding storage was an hack
- 21. Lists • In-the-middle accesses are O(N) • No fixed entires offsets • Good for pop/push workloads
- 22. ADT: Streams are logs
- 23. Log file • One (complex) entry per line • Ordered • One entry one offset • Repeated entries are OK • Memory efficient
- 24. An abstract log file • Entries are hashes • Offsets are logical (entry unique ID) • O(log N) access to random ranges • Trow away old data easily • Memory efficient? Yep!
- 27. Streams API TAPPEND key sensor 01 temperature 35.6 > 1486475519747.0
- 28. Streams API • Blocking API: consume from <ID> • Ranges • Deletion of old data • From Kafka: consumer groups • ACK and retry
- 29. Thank You Salvatore Sanfilippo Redis Labs Tweet me at @antirez