NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



Quick Guide to Using MongoDB With Django

In this article, learn how to call MongoDB from Python (using MongoEngine), and integrate it into a Django project in lieu of the built-in ORM. A sample web interface for creating, reading, writing, and updating data to the MongoDB back end is included.

When I’m thinking of Django (and Rails) one of its major strengths is the ease of defining mappings for the application entities and the way these mappings integrate with both the persistence layer and presentation layer. But the document model is introducing a lot of different options and approaches when compared with the relational model (which is the default in Django). Support for simple mappings is a good start, but I don’t think MongoDB integration supports yet optional fields, or entity versioning, or custom aggregate entity mappings, or tunable queries.

Original title and link: Quick Guide to Using MongoDB With Django (NoSQL database©myNoSQL)