From Memcached to Redis to Surpdb  Posted on by  In this post,
I'll describe my journey to find the perfect caching solution
for my Django-based site linkrdr. After trying Memcached and
Redis, I settled on surpdb. I guarantee you haven't heard of
surpdb before, because I just finished writing it.  Querying and
retrieving large data sets is not the Django ORM's sweet-spot.
There are a number of reasons why Django's QuerySets struggle
with large amounts of data, but the primary reason is because it
wasn't designed to work in that way. For linkrdr, retrieving and
analyzing a user's data became too much for all previous
attempts at marrying Django QuerySets with some form of caching.
Caching in Memcached to avoid going to the database on
subsequent calls worked well except in one regard: the first
request took so long that it would time out, resulting in a user
never being able to see their data.  Enter Redis. Current
sweetheart of the NoSQL movement, Redis is a key-value store
that resides entirely in resident m