Why Django Sucks, and How we Can Fix it. Python Datastructures Backed by Redis @ Irrational Exuberance. I've been working with Redis quite a bit at work lately, and I've really taken to it. At some point it occurred to me that it would be terribly straightforward to use Redis as the backend for the most common Python datastructures, lists and dictionaries. Not only easy, but doing so would even provide some benefits: readability, distribution across processes/threads/machines, and familiarity with the existing interfaces. The code resulting from these ideas is available on Github. Before you run off, let's consider a few simple but powerful applications of this approach: a shared configuration mechanism and ye olde publisher-consumer example.
Shared Configuration Once you start working at scale, managing shared configuration data becomes an increasingly important problem. Pretty straightforward. Distributed Producers and Consumers At a certain point most architectures are in dire need of a message queue. Ok. Pydanny's django-uni-form at master - GitHub. Django-pki - Project Hosting on Google Code. Django Packages : Welcome.