Tornado, the non-blocking web server and tools open sourced by FriendFeed before their acquisition, seems to get some NoSQL activity. While Django is leading the way in the Python world, judging by the NoSQL projects happening around Node.js, one could say that Tornado, with its non-blocking architecture, may be an interesting alternative.

Thomas Pelletier has ☞ a blog post about a simple websocket + Tornado + Redis Pub/Sub protocol integration:

The principle is very simple: when your user loads the page, she is automatically added to a list of “listeners”. An independent thread is running: it listens for messages from Redis with the subscribe command, and send a message through Websocket to every registered ”listener”. In this example, the user can send a message to herself with a simple AJAX-powered form, which calls a view with a payload (the message), and the view publish it via the publish command of Redis.

This is basically a web chat! If you want to have fun, you can then add a roster, with a presence system, authentication etc…

There’s also a ☞ GitHub project called Trombi:

Trombi is an asynchronous CouchDB client for Tornado.

And I’m pretty sure there are other projects I’ve missed (but you can leave a comment to add them to the list).

Original title and link for this post: Tornado Sees Some NoSQL Activity (published on the NoSQL blog: myNoSQL)

Gleicon Moraes’ slide deck about RestMQ, an HTTP/Redis based message queue. More about RestMQ can be found ☞ here and the source code is available on ☞ GitHub.

Keep in mind that Redis-backed queues is one very often cited use case for Redis.

Original title and link for this post: Presentation: RestMQ - HTTP/Redis based Message Queue (published on the NoSQL blog: myNoSQL)

Firstly, Diarmuid Bourke’s presentation at PyCon Irland 2010:

Mike Dirolf ☞ covers the details of working with PyMongo and replica sets, one of the most interesting features in the MongoDB 1.6 releases:

PyMongo makes working with replica sets easy. Here we’ll launch a new replica set and show how to handle both initialization and normal connections with PyMongo.

And in case you’d like to learn some more you can also check:

• MongoDB for Python or Ruby: your Choice
• Python, Django, and MongoDB

Original title and link for this post: MongoDB with Python (published on the NoSQL blog: myNoSQL)

Django decided long time ago that Ruby on Rails cannot be the only framework where people can have fun integrating with all NoSQL databases. During this year DjangoCon Europe there were several session dedicated to Django and NoSQL databases:

• Alex Gaynor: What NoSQL support in the Django ORM looks like, and how do we get there
• Peter Bengtsson: Using MongoDB in your app
• Benoît Chesneau: Relax your project with CouchDB
• Tobias Ivarsson: Django and Neo4j: Domain Modeling that Kicks Ass
• Django and NoSQL Panel

What NoSQL support in the Django ORM looks like, and how do we get there

Alex Gaynor speaks about what needs to change in Django ORM to make it more NoSQL friendly:

Reinout van Rees has a summary of the talk ☞ here.

Using MongoDB in your app

Peter Bengtsson talks about his experience of passing from using ZODB for the last 10 years to MongoDB

Some notes from the talk are available ☞ here.

Relax your project with CouchDB

Benoît Chesneau talks about what makes CouchDB appealing to python developers. He also covers the CouchDBkit python framework.

Django and Neo4j: Domain Modeling that Kicks Ass

Not coming from DjangoCon, but still about Django and Neo4j, is Tobias Ivarsson’s presentation: “Django and Neo4j - Domain modeling that kicks ass”:

Derek Stainer summarizes the slide deck ☞ here.

Django and NoSQL Panel

A fantastic panel on the future of Django and NoSQL databases that you can watch over ☞ blip.tv. Reinout van Rees published a transcript of the panel ☞ here.

All in all a lot of NoSQL excitement in the Django world! Or should it be the opposite?

Update: Here is the latest Django and NoSQL Databases status update

Django and NoSQL Databases Revisited originally posted on the NoSQL blog: myNoSQL

1. Tarek Ziadé: ☞ A Firefox plugin experiment. XUL, Bottle and Redis ¶
2. Andreas Jung: ☞ Looking beyond one’s own nose - looking at RabbitMQ and MongoDB ¶

   Unsorted remarks on RabbitMQ and MongoDB plus some benchmarks with mass data

3. Franck Cuny: ☞ presque, a Redis / Tatsumaki based message queue. Perl and Redis baby! ¶
4. Mark Atwood: ☞ Reacting to “Memcached is not a store”. IMO, it is as much as a store as any dict/hash you’ve been using. Well, a bit more. ¶
5. okram: ☞ pipes. A lot of activity around graph databases lately: ¶

   Pipes is a graph-based data flow framework written in Java 1.6+. A process graph (also known as a Kahn process network) is composed of a set of process vertices connected to one another by a set of communication edges. Each process can run independent of the others and as such, concurrency is a natural consequence as data is transformed in a pipelined fashion from input to output.

Mirko Froehlich has a ☞ long post explaining the problem and the rationale behind the chosen architectures. Then, he goes on presenting the various pieces used in building the solution:

• ☞ TweetStream: Ruby library for Twitter streaming API
• Redis used as a queue
• ☞ Sinatra
• ☞ jQuery
• deployment: ☞ nginx + ☞ Passenger + ☞ Capistrano + ☞ God

Code is available on ☞ GitHub.

Bulkan Evcimen took this sample application and built it on a Python stack:

• ☞ tweetstream: Python lib for Twitter streaming API
• Redis over redis-py
• ☞ CherryPy: web app framework. As a side note, there is a Python framework very similar to Sinatra called Bottle
• ☞ Jinja2: HTML templating
• ☞ jQuery

So now you have yet another “good” reason^[1] to play with Redis and Twitter.