I agree, with the exception in the case of a single web process, I wouldn't use memcached but just rely on dogpile memory backend, which is about the same (unle

I agree, with the exception in the case of a single web process, I wouldn't use memcached but just rely on dogpile memory backend, which is about the same (unless I'm proven wrong :p). I'd use memcached otherwise to share the benefit of caching poll. Caching in redis, I'm not fan, since redis will write to your drive at one point (a large cache would impact your drive space and slow down redis start dramatically). I share your opinion on lazy loading, whenever possible you should know in advance if you're gonna need that related information before you pull your data: it's much faster to chain 2 select in one call (even with a connection pool). That being said, I love redis and wish I could use it for all my objects (I could, since all my objects have a pk) but it lacks some fondamental real world features (relationships and transactions) that make business query/analytic a nightmare (who connect to your website, at what rate...) while Relational database does an amazing job at it.