MongoAdmin. Introducing a new admin interface for MongoDB, written in Python using Django and Bootstrap.
License Great! Hi, [ Popular Links: mongoDB ~ the good to begin links. Sunday, May 20, 2012 mongoDB ~ the good to begin links mongoDB Download (OSX/Win/Linux/Solaris/Source): Cloud MongoDB Hosting (240MB Free): MongoDB vs Cassandra vs CouchDB vs Riak vs Neo4j vs Redis vs HBase vs MemBase: Home of Documentation by MongoDB's Admin Zone Quick Support Little MongoDB Book (free e-book): MongoDB Drivers for different Programming Platforms: High Availability & Replicasets:slideshare.net high-availabiltity-replica-sets-with-mongodb MongoDB for Graylog: Specific Links for Specific Problems Performance Analysis Security in MongoDB Practical MongoDB (windows oriented): #1 methodicmadness.com/2010/06/practical-mongodb-part-1-up-and-running.html.
Production Deployments. MongoDB, Morphia and EmbedMongo » The Cubeia Blog. Most of the times when working with online games we run into the need to persist data that is produced by the games.
This can be anything from hand history to game state to audit trails for remote calls to other systems. But what they usually have in common is that it is high volume writes, hardly any updates, some reads and that the data has large variation in what we need to store even if it is within the same context. That last part about the data having variations is what makes this interesting. Take hand history for instance, we want to save events that are executed on a Poker table. On a Poker table many things happens – player join and leave the table, bets are made, cards are dealt, players get more chips etc. etc.
If we were to use a relational database we might end up with a single table with an ungodly amount of columns so that each event has all its specific columns available. But what about this NOSQL stuff I have heard so much about? You Only Wish MongoDB Wasn't Relational. MongoDB = Get Stuff Done Update: Changed blog example to use a normal belongs-to relationship.
Update: Added examples of $slice and $elemMatch to show why they don’t work When choosing the stack for our TV guide service, we became interested in NoSQL dbs because we anticipated needing to scale horizontally. We evaluated several and settled on MongoDB. The main reason was that MongoDB got out of the way and let us get work done. So when you read that MongoDB is a document store, you might get the wonderful idea to store your relationships in a big document. Several times, we’ve excitedly begun a schema this way, only to be forced to pull the nested documents out into their own collection. Let’s make a blog! Here’s an example. What’s a blog without comments? This works nicely with the key/value idea that you should denormalize your data.
When Nested Documents Become a Problem The minute you need just a little control over querying against those comments, you’re stuck. Collections are Cheap.
The MongoDB Collection. MongoDB Interactive Tutorial. MongoDB. MongoDB | node.js - Plugins/Etc.