MongoDB wasn't designed in a lab. We built MongoDB from our own experiences building large scale, high availability, robust systems. We didn't start from scratch, we really tried to figure out what was broken, and tackle that. So the way I think about MongoDB is that if you take MySql, and change the data model from relational to document based, you get a lot of great features: embedded docs for speed, manageability, agile development with schema-less databases, easier horizontal …
…sort of schema free cousins of relational databases: CouchDb, Riak, MongoDb, etc. Simple to understand and richer than plain key-value stores.
Disk vs. Memory: A third useful dimension is whether the database is memory-driven or disk-driven. This is important since in the latter case you need an explicit cache, while in the former case you are not durable:
Memory
Disk
Scalaris
CouchDb
MongoDb…
I could use at least a small slowing-down of the treadmill for a day or two.
How I reduced translation costs of 200 articles from $ 9000 to $ 46 - Second Life as an alternative to Mechanical Turk.
Notes from a production MongoDB deployment - Some detailed stories from the trenches.
Rapid prototyping with HAML, SASS and Ruby - A workflow for coming up with web site designs.
Erector - Builder-like view framework for object-oriented HTML composition.
Document stores: Couch DB, MongoDB, and SimpleDB.
Record stores: BigTable, HBase, HyperTable, and Cassandra.
Scalable RDBMSs: MySQL Cluster, ScaleDB, Drizzle, and VoltDB.
The paper describes each system and then compares them on the dimensions of Concurrency Control, Data Storage Replication, Transaction Model, General Comments, Maturity, K-hits, License Language.
And the winner is: there are no winners. Yet. Rick concludes by pointing to a great convergence: …
Being a binary format, MongoDB doesn't have to parse documents like with JSON, they're a valid in-memory presentation already when coming across the wire.
References
Documents can embed a tree of associated data, e.g. tags, comments and the like instead of storing them in different MongoDB documents. This is not specific to MongoDB, but document databases in general (see [5] ), but when using find you can dereference nested objects with the dot, e.g. blog.posts.comments.body, …
So last night I realized that I really love MongoDB. I love it so much that I want everyone to be using it whenever it makes sense (which is quite often). I thought about what I could do to help get the word out more and starting a new site made the most sense (instead of flooding RailsTips with Mongo stuff).
MongoTips is a new blog dedicated to MongoDB news and information. I'll be posting things there that we have learned building Harmony and anything I can find from the community.
No tool is like the other. Just comparing e.g. MongoDB, Redis and MySQL is the wrong way to approach your problem, especially if you just look at speed and comparing their feature set. Feature sets and speed are usually different for a reason. Instead you should be comparing every tool with your data. How much do you need to bend the data to store and access it easily. Is it even possible to store it efficiently and or your particular use case? Are potential trade-offs (e.g. data duplication …
…MongoDB, an open-source, document-based database. We started 10gen and started working on MongoDB mostly out of our own frustrations after building scalable web infrastructure for a dozen years.
It really just came to a point where we were constantly fighting the same battles and building one-off solutions to handle functional gaps in relational databases. We started building MongoDB about two years ago, and we launched it earlier this year. People are getting very excited about it.
It's …
…years, people have created a number of ActiveRecord lookalike libraries for things like MongoDB or CouchDB. In Rails 3, we have extracted elements of ActiveRecord unrelated to RDBMS persistence, such as validations, callbacks, dirty tracking, and serialization into a separate library. Other libraries, or even plain old Ruby code, can use these components on an à la carte basis, choosing to look as much or as little like ActiveRecord as they wish.
Additionally, ActiveModel defines …
…description mentions Rails, Merb, Sinatra, CouchdB, MongoDB, Redis, AWS. All these Ruby technologies are actually already used in production or are being seriously evaluated.
I'm also really looking forward to join the existing team. I know I'm going to love working with a bunch of awesome developers coming from various backgrounds.
Those who know me, know that I'm not a morning person. And while your typical office job is categorized as ‘9-5′, don't feel …