If Modified Since for Redis
Caching is everywhere! It is an essential part of most applications out there and so obviously there are a lot of options you can chose from. Here is a non exhaustive list:
And caching is very specific to the kind of data you are transfering (JSON, video, ...) and to your architecture.
That's a lot of choices to make !
At E4E, since we are a stratup we can't take the risk to over engineer this. I will cost us time, money and make our architecture way harder to maintain. So we developed a simple Redis plugin to help us with caching.
As I said, caching is very specific to your solution, there is no One size fits all solution. So let's see what our solution is providing first.
At E4E we provide educational video content for students in Ethiopia through an native Android app called Saquama. Every video comes with some metadata like: Title, Description and all the relational part that comes with it. For this article we are focusing on these metadata because videos are already taken care of by a CDN.
What about the plugin?
RedisIMS standing for Redis If Modified Since (very creative, isn't it ?), provides a HTTP protocol's If Modified Since Header like experience. This basically means that we have a timestamp saying when our metadata about a certain video changed. We can then compare this timestamp with the one sent by the client and returns a value accordingly.
How does that work ? Technically I mean.
This plugin is heavily influenced by the following Lua code in this article. The process consist in the following actions:
When caching some data, the plugin will do a HSET of the key defined in the plugin, the data and the timestamp.
When getting cached data, the plugin will use HGET with the key defined and the timestamp.
- If the data doesn't exist, return NULL
- If the data exists and the timestamp is bigger or equal than the cached one, we return NULL
- and If the timestamp is smaller than the cached one, we return the cached data
If you feel like contributing to the project or just trying it, head up to the Github repository.
And finnaly if you have any constructive feedback, feel free to reach me by checking the contact page of either my Github profile or the about page of the website