Redis was born as a persistent Memcached. It is because of that shady past that a lot of developers consider it solely as an alternative caching approach. However, Redis quickly evolved to a very flexible database server.
Redis offers atomic operations over a wide variety of primitive data types (strings, lists, sets, ordered sets, and hashes) that offer a lot of flexibility and allow us to think and implement the best possible approach to store our application data. This, together with other highly celebrated features (such as replication, two different persistence strategies, transactions, and Lua based scripting) makes Redis a very interesting database for our projects.
In this session we will explore, using practical examples, the most frequent problems almost all web applications face, and how we can use Redis to solve them. We will also show the most common pitfalls and what strategies we can use to avoid them.