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.
Rate limiting/monitoring with Redis
As a system grows and moves towards a Service Oriented Architecture, there is generally a need to monitor and limit the access rates of different modules or services. This session will be about a redis recipe for implementing a lightweight and generic rate limiting/monitoring library. The simplicity of redis data structures, persistence and its in memory speed makes it a perfect datastore for this use case.
This library is currently used in production@Capillary and handles a sustained average traffic of around 16000 request per second across all services.
The session would talk about live scenarios@Capillary such as :
Limiting the sms/emails sent to a customer based on the configured limits.
AppID level monitoring and rate limiting in our consumer apps such as the eCommerce widgets.
Monitoring the usage of different APIs across clients, customer communications and user statistics. These hit rates can be easily visualized on a dashboard UI.
All of these uses cases are catered by a single generic library backed up by redis.
The session would also cover the basic low level data model, commands, the data structures used, different design iterations the library went through for improved performance.
I’m a developer at Capillary Technologies. My colleague, Souvik Roy would also be part of the talk.