Redis is an advanced key-value store NoSQL database, often used as a cache (replacing Memcache) and messaging layer (replacing various message queues) in web apps.
As the glue that binds together larger components, Redis rarely gets the attention it deserves. You can be a hotshot NodeJS ninja or PostgreSQL guru, but without Redis your web app is unlikely to be scalable. Knowing what Redis is, how it works and how to use it effectively is an essential skill for any web developer.
Join us for the second Miniconf of 2014 as we examine Redis in detail. We’ve learnt from the first edition with AngularJS and restructured the day:
- The first half of the day will be a workshop for beginners, helping you get familiar with Redis, the data structures, API and command line. Advanced users can skip this.
- The second half of the day will be showcases by advanced Redis users, explaining how Redis glues their website together.
- The final part of the day is an open forum for any participant to open up their code and have their concerns addressed by an advanced user.
Ticketing is now closed. The event is sold out.
Redis Memory Optimization
- Diagnose and identify memory problems in Redis
- Design data structures to get the best performance from Redis.
The session assumes participants are familiar with Redis and its data structures.
- Overview of Redis internal data structues (Integer Set, Zipmap & Ziplist, Hashmap, SkipLists, Double Linked Lists and so on)
- What can a developer do to reduce memory usage?
- How do you diagnose memory problems in production?
(DRAFT - Will be refined later)
I am the author of Redis RDB Tools, a library to work with Redis Dump Files. Among other things, rdbtools provides a memory profiler for Redis. Over the years, Rdbtools has helped many companies to diagnose memory problems.
I am also an active member of the Redis community. I am frequently seen on StackOverflow, answering questions on Redis. Here is quick link to all my answers on stackoverflow
By day, I am Co-founder and Director Engineering at HashedIn Technologies. My role involves designing large scale systems with great performance and high availability. I routinely use Redis as an object cache, as a queue, and for its pub-sub capabilities.