developer toolbox

http://www.mongodb.org/ (agpl 3 license)

http://github.com/mongodb/mongo-ruby-driver/ ruby driver (apache 2.0 license)

Mongo currently has client support for the following programming languages:

• Ruby
• Python
• Java
• C++
• PHP
• Perl
• V8 Javascript - enquire in the user forums for more information

http://github.com/mongodb/mongo/tree/master

http://blog.mongodb.org/

AGPL - why¶

MongoDB is released under the GNU Affero General Public License. This Free Software Foundation license is fairly new, and thus we wanted to talk about how this license differs from GPL.

Our goal with using AGPL is to preserve the concept of copyleft with MongoDB. With traditional GPL, copyleft was associated with the concept of distribution of software. The problem is that nowadays, distribution of software is rare: things tend to run in the cloud. AGPL fixes this “loophole” in GPL by saying that if you use the software over a network, you are bound by the copyleft. Other than that, the license is virtually the same as GPL v3.

http://github.com/squeejee/floxee/tree/master

http://twitter.com/floxee

mongodb-user google group

We're in the process of doing some. You can find current results here.

http://www.mongodb.org/display/DOCS/Performance+Testing

The "problem" is that MongoDB is so fast, performance tends to be
limited by driver performance :)

The main differences between MongoDB and CouchDB are speed and query
model.

1) MongoDB is very, very fast. We can do inserts north of 20k/sec,
where on CouchDB on the same hardware, about 250-300/sec is the max.

2) The query models are quite different - MongoDB has a query model
that is direct, uses indexes, and very similar to the model you might
be used to in an RDBMS (doesn't use SQL though). CouchDB uses a
"view" system which, while very nice, doesn't allow arbitrary queries,
and limits to what you can express in a key/value lookup.

Also, MongoDB's storage format - while akin to JSON - goes beyond JSON
by adding a few types like date, which is important for querying...

I guess just as important a question... what problem are you trying to
solve? What do you plan on using the DB for?

geir

On Mar 3, 2009, at 3:48 AM, Voltron wrote:

Could someone tell me if there are benchmarks using MongoDB and the
the advantages of MongoDB against somethimg like CouchDB?

Thanks

http://www.viget.com/extend/getting-started-with-mongodb-mongomapper/

Clinton R. Nixon, Development Director, September 17, 2009 23

• MongoDB has collections of data, not tables. Unlike CouchDB, which is also a document-oriented DB, Mongo has namespaces for data. These are schema-less, so any data could go in each namespace. In my practice, I’ve persisted objects of one class into each collection, not unlike ActiveRecord with MySQL or any other RDBMS.
• MongoDB has indexes. Even though each collection has no schema, you can still index the data in a collection based off a field. Not all documents in a collection have to have this field.
• MongoDB has a query language and query profiling. While you can use JavaScript to search through a collection, like CouchDB, you also have access to a rich query language that can filter based on fields, like SQL, and filter based on the contents of embedded documents, which proves to be totally freaking awesome. Instead of a complex join, you can query for all documents in the posts collection that have an embedded comment in the last month.

Given the similarities between MongoDB and a relational database, you’d think it would be easy to use in Ruby in place of ActiveRecord, and you’d be right. John Nunemaker has created a gem called MongoMapper to work as an object mapper to MongoDB. Using MongoMapper, you can create model classes like so:

class Book
  include MongoMapper::Document

  key :title, String, :required => true
  key :author, String
  key :published_at, Date
  key :user_id, String
  timestamps! # HECK YES

  belongs_to :user
  many :chapters
end 

http://github.com/guillaumerose/bind9-mongodb