Mongodb

About This Book
License
The Little MongoDB Book book is licensed under the Attribution-NonCommercial 3.0 Unported
license. You should not have paid for this book.

You are basically free to copy, distribute, modify or display the book. However, I ask that you
always attribute the book to me, Karl Seguin and do not use it for commercial purposes.

You can see the full text of the license at:

http://creativecommons.org/licenses/by-nc/3.0/legalcode

About The Author
Karl Seguin is a developer with experience across various fields and technologies. He's an
expert .NET and Ruby developer. He's a semi-active contributor to OSS projects, a technical
writer and an occasional speaker. With respect to MongoDB, he was a core contributor to the
C# MongoDB library NoRM, wrote the interactive tutorial mongly as well as the Mongo Web
Admin. His free service for casual game developers, mogade.com, is powered by MongoDB.

His blog can be found at http://openmymind.net, and he tweets via @karlseguin

With Thanks To
A special thanks to Perry Neal for lending me his eyes, mind and passion. You provided me
with invaluable help. Thank you.

Latest Version
The latest source of this book is available at:

http://github.com/karlseguin/the-little-mongodb-book.

2

Introduction
It's not my fault the chapters are short, MongoDB is just easy to learn.

It is often said that technology moves at a blazing pace. It's true that there is an ever grow-
ing list of new technologies and techniques being released. However, I've long been of the
opinion that the fundamental technologies used by programmers move at a rather slow pace.
One could spend years learning little yet remain relevant. What is striking though is the speed
at which established technologies get replaced. Seemingly over-night, long established tech-
nologies find themselves threatened by shifts in developer focus.

Nothing could be more representative of this sudden shift than the progress of NoSQL tech-
nologies against well-established relational databases. It almost seems like one day the web
was being driven by a few RDBMS' and the next, five or so NoSQL solutions had established
themselves as worthy solutions.

Even though these transitions seem to happen overnight, the reality is that they can take
years to become accepted practice. The initial enthusiasm is driven by a relatively small set
of developers and companies. Solutions are refined, lessons learned and seeing that a new
technology is here to stay, others slowly try it for themselves. Again, this is particularly true
in the case of NoSQL where many solutions aren't replacements for more traditional storage
solutions, but rather address a specific need in addition to what one might get from traditional
offerings.

Having said all of that, the first thing we ought to do is explain what is meant by NoSQL. It's
a broad term that means different things to different people. Personally, I use it very broadly
to mean a system that plays a part in the storage of data. Put another way, NoSQL (again,
for me), is the belief that your persistence layer isn't necessarily the responsibility of a single
system. Where relational database vendors have historically tried to position their software as
a one-size-fits-all solution, NoSQL leans towards smaller units of responsibility where the best
tool for a given job can be leveraged. So, your NoSQL stack might still leverage a relational
databases, say MySQL, but it'll also contain Redis as a persistence lookup for specific parts of
the system as well as Hadoop for your intensive data processing. Put simply, NoSQL is about
being open and aware of alternative, existing and additional patterns and tools for managing
your data.

You might be wondering where MongoDB fits into all of this. As a document-oriented database,
Mongo is a more generalized NoSQL solution. It should be viewed as an alternative to relational
databases. Like relational databases, it too can benefit from being paired with some of the
more specialized NoSQL solutions. MongoDB has advantages and drawbacks, which we'll cover
in later parts of this book.

As you may have noticed, we use the terms MongoDB and Mongo interchangeably.

3

Getting Started
Most of this book will focus on core MongoDB functionality. We'll therefore rely on the MongoDB
shell. While the shell is useful to learn as well as being a useful administrative tool, your code
will use a MongoDB driver.

This does bring up the first thing you should know about MongoDB: its drivers. MongoDB has
a number of official drivers for various languages. These drivers can be thought of as the
various database drivers you are probably already familiar with. On top of these drivers, the
development community has built more language/framework-specific libraries. For example,
NoRM is a C# library which implements LINQ, and MongoMapper is a Ruby library which is
ActiveRecord-friendly. Whether you choose to program directly against the core MongoDB
drivers or some higher-level library is up to you. I point this out only because many people
new to MongoDB are confused as to why there are both official drivers and community libraries -
the former generally focuses on core communication/connectivity with MongoDB and the latter
with more language and framework specific implementations.

As you read through this, I encourage you to play with MongoDB to replicate what I demon-
strate as well as to explore questions that might come up on your own. It's easy to get up
and running with MongoDB, so let's take a few minutes now to set things up.

1. Head over to the official download page and grab the binaries from the first row (the rec-
ommended stable version) for your operating system of choice. For development purposes,
you can pick either 32-bit or 64-bit.

2. Extract the archive (wherever you want) and navigate to the bin subfolder. Don't execute
anything just yet, but know that mongod is the server process and mongo is the client shell
- these are the two executables we'll be spending most of our time with.

3. Create a new text file in the bin subfolder named mongodb.config

4. Add a single line to your mongodb.config: dbpath=PATH_TO_WHERE_YOU_WANT_TO_STORE_YOUR_DATABASE_F
. For example, on Windows you might do dbpath=c:mongodbdata and on Linux you might
do dbpath=/etc/mongodb/data.

5. Make sure the dbpath you specified exists

6. Launch mongod with the --config /path/to/your/mongodb.config parameter.

As an example for Windows users, if you extracted the downloaded file to c:mongodb and you
created c:mongodbdata then within c:mongodbbinmongodb.config you would specify
dbpath=c:mongodbdata. You could then launch mongod from a command prompt via c:
mongodbbinmongod --config c:mongodbbinmongodb.config.

Feel free to add the bin folder to your path to make all of this less verbose.

4

Hopefully you now have MonogDB up and running. If you get an error, read the output carefully
- the server is quite good at explaining what's wrong.

You can now launch mongo (without the d) which will connect a shell to your running server.
Try entering db.version() to make sure everything's working as it should. Hopefully you'll
see the version number you installed.

5

Chapter 1 - The Basics
We begin our journey by getting to know the basic mechanics of working with MongoDB.
Obviously this is core to understanding MongoDB, but it should also help us answer higher-
level questions about where MongoDB fits.

To get started, there are six simple concepts we need to understand.

1. MongoDB has the same concept of a `database' with which you are likely already familiar
(or a schema for you Oracle folks). Within a MongoDB instance you can have zero or more
databases, each acting as high-level containers for everything else.

2. A database can have zero or more `collections'. A collection shares enough in common
with a traditional `table' that you can safely think of the two as the same thing.

3. Collections are made up of zero or more `documents'. Again, a document can safely be
thought of as a `row'.

4. A document is made up of one or more `fields', which you can probably guess are a lot like
`columns'.

5. `Indexes' in MongoDB function much like their RDBMS counterparts.

6. `Cursors' are different than the other five concepts but they are important enough, and
often overlooked, that I think they are worthy of their own discussion. The important thing
to understand about cursors is that when you ask MongoDB for data, it returns a cursor,
which we can do things to, such as counting or skipping ahead, without actually pulling
down data.

To recap, MongoDB is made up of databases which contain collections. A collection is
made up of documents. Each document is made up of fields. Collections can be indexed,
which improves lookup and sorting performance. Finally, when we get data from MongoDB we
do so through a cursor whose actual execution is delayed until necessary.

You might be wondering, why use new terminology (collection vs. table, document vs. row and
field vs. column). Is it just to make things more complicated? The truth is that while these
concepts are similar to their relational database counterparts, they are not identical. The core
difference comes from the fact that relational databases define columns at the table level
whereas a document-oriented database defines its fields at the document level. That is to
say that each document within a collection can have its own unique set of fields. As such,
a collection is a dumbed down container in comparison to a table, while a document has a
lot more information than a row.

Although this is important to understand, don't worry if things aren't yet clear. It won't take
more than a couple of inserts to see what this truly means. Ultimately, the point is that a

6

collection isn't strict about what goes in it (it's schema-less). Fields are tracked with each
individual document. The benefits and drawbacks of this will be explored in a future chapter.

Let's get hands-on. If you don't have it running already, go ahead and start the mongod server
as well as a mongo shell. The shell runs JavaScript. There are some global commands you
can execute, like help or exit. Commands that you execute against the current database
are executed against the db object, such as db.help() or db.stats() . Commands that you
execute against a specific collection, which is what we'll be doing a lot of, are executed against
the db.COLLECTION_NAME object, such as db.unicorns.help() or db.unicorns.count().

Go ahead and enter db.help(), you'll get a list of commands that you can execute against
the db object.

A small side note. Because this is a JavaScript shell, if you execute a method and omit the
parentheses (), you'll see the method body rather than executing the method. I only mention
it because the first time you do it and get a response that starts with function (...){ you
won't be surprised. For example, if you enter db.help (without the parentheses), you'll see
the internal implementation of the help method.

First we'll use the global use method to switch databases, go ahead and enter use learn. It
doesn't matter that the database doesn't really exist yet. The first collection that we create
will also create the actual learn database. Now that you are inside a database, you can start
issuing database commands, like db.getCollectionNames(). If you do so, you should get an
empty array ([ ]). Since collections are schema-less, we don't explicitly need to create them.
We can simply insert a document into a new collection. To do so, use the insert command,
supplying it with the document to insert:

db.unicorns.insert({name: 'Aurora', gender: 'f', weight: 450})

The above line is executing insert against the unicorns collection, passing it a single argu-
ment. Internally MongoDB uses a binary serialized JSON format. Externally, this means that
we use JSON a lot, as is the case with our parameters. If we execute db.getCollectionNames
() now, we'll actually see two collections: unicorns and system.indexes. system.indexes
is created once per database and contains the information on our databases index.

You can now use the find command against unicorns to return a list of documents:

db.unicorns.find()

Notice that, in addition to the data you specified, there's an _id field. Every document must
have a unique _id field. You can either generate one yourself or let MongoDB generate an
ObjectId for you. Most of the time you'll probably want to let MongoDB generate it for you.
By default, the _id field is indexed - which explains why the system.indexes collection was
created. You can look at system.indexes:

db.system.indexes.find()

7

What you're seeing is the name of the index, the database and collection it was created against
and the fields included in the index.

Now, back to our discussion about schema-less collections. Insert a totally different document
into unicorns, such as:

db.unicorns.insert({name: 'Leto', gender: 'm', home: 'Arrakeen', worm: false})

And, again use find to list the documents. Once we know a bit more, we'll discuss this
interesting behavior of MongoDB, but hopefully you are starting to understand why the more
traditional terminology wasn't a good fit.

Mastering Selectors
In addition to the six concepts we've explored, there's one practical aspect of MongoDB you
need to have a good grasp of before moving to more advanced topics: query selectors. A
MongoDB query selector is like the where clause of an SQL statement. As such, you use it
when finding, counting, updating and removing documents from collections. A selector is a
JSON object , the simplest of which is {} which matches all documents (null works too). If
we wanted to find all female unicorns, we could use {gender:'f'}.

Before delving too deeply into selectors, let's set up some data to play with. First, remove
what we've put so far in the unicorns collection via: db.unicorns.remove() (since we aren't
supplying a selector, it'll remove all documents). Now, issue the following inserts to get some
data we can play with (I suggest you copy and paste this):

db.unicorns.insert({name: 'Horny', dob: new Date(1992,2,13,7,47), loves: ['
carrot','papaya'], weight: 600, gender: 'm', vampires: 63});
db.unicorns.insert({name: 'Aurora', dob: new Date(1991, 0, 24, 13, 0), loves:
['carrot', 'grape'], weight: 450, gender: 'f', vampires: 43});
db.unicorns.insert({name: 'Unicrom', dob: new Date(1973, 1, 9, 22, 10), loves:
['energon', 'redbull'], weight: 984, gender: 'm', vampires: 182});
db.unicorns.insert({name: 'Roooooodles', dob: new Date(1979, 7, 18, 18, 44),
loves: ['apple'], weight: 575, gender: 'm', vampires: 99});
db.unicorns.insert({name: 'Solnara', dob: new Date(1985, 6, 4, 2, 1), loves:['
apple', 'carrot', 'chocolate'], weight:550, gender:'f', vampires:80});
db.unicorns.insert({name:'Ayna', dob: new Date(1998, 2, 7, 8, 30), loves: ['
strawberry', 'lemon'], weight: 733, gender: 'f', vampires: 40});
db.unicorns.insert({name:'Kenny', dob: new Date(1997, 6, 1, 10, 42), loves: ['
grape', 'lemon'], weight: 690, gender: 'm', vampires: 39});
db.unicorns.insert({name: 'Raleigh', dob: new Date(2005, 4, 3, 0, 57), loves:
['apple', 'sugar'], weight: 421, gender: 'm', vampires: 2});
db.unicorns.insert({name: 'Leia', dob: new Date(2001, 9, 8, 14, 53), loves: ['
apple', 'watermelon'], weight: 601, gender: 'f', vampires: 33});
db.unicorns.insert({name: 'Pilot', dob: new Date(1997, 2, 1, 5, 3), loves: ['
apple', 'watermelon'], weight: 650, gender: 'm', vampires: 54});

8

db.unicorns.insert({name: 'Nimue', dob: new Date(1999, 11, 20, 16, 15), loves:
['grape', 'carrot'], weight: 540, gender: 'f'});
db.unicorns.insert({name: 'Dunx', dob: new Date(1976, 6, 18, 18, 18), loves: [
'grape', 'watermelon'], weight: 704, gender: 'm', vampires: 165});

Now that we have data, we can master selectors. {field: value} is used to find any docu-
ments where field is equal to value. {field1: value1, field2: value2} is how we do an
and statement. The special $lt, $lte, $gt, $gte and $ne are used for less than, less than or
equal, greater than, greater than or equal and not equal operations. For example, to get all
male unicorns that weigh 700 pounds, we could do:

db.unicorns.find({gender: 'm', weight: {$gt: 700}})
//or (not quite the same thing, but for demonstration purposes)
db.unicorns.find({gender: {$ne: 'f'}, weight: {$gte: 701}})

The $exists operator is used for matching the presence or absence of a field, for example:

db.unicorns.find({vampires: {$exists: false}})

Should return a single document. If we want to OR rather than AND we use the $or operator
and assign it to an array of values we want or'd:

db.unicorns.find({gender: 'f', $or: [{loves: 'apple'}, {loves: 'orange'}, {
weight: {$lt: 500}}]})

The above will return all female unicorns which either love apples or oranges or weigh less
than 500 pounds.

There's something pretty neat going on in our last example. You might have already noticed,
but the loves field is an array. MongoDB supports arrays as first class objects. This is an
incredibly handy feature. Once you start using it, you wonder how you ever lived without
it. What's more interesting is how easy selecting based on an array value is: {loves: '
watermelon'} will return any document where watermelon is a value of loves.

There are more available operators than what we've seen so far. The most flexible being
$where which lets us supply JavaScript to execute on the server. These are all described in
the Advanced Queries section of the MongoDB website. What we've covered so far though is
the basics you'll need to get started. It's also what you'll end up using most of the time.

We've seen how these selectors can be used with the find command. They can also be
used with the remove command which we've briefly looked at, the count command, which we
haven't looked at but you can probably figure out, and the update command which we'll spend
more time with later on.

The ObjectId which MongoDB generated for our _id field can be selected like so:

9

db.unicorns.find({_id: ObjectId("TheObjectId")})

In This Chapter
We haven't looked at the update command yet, or some of the fancier things we can do with
find. However, we did get MongoDB up and running, looked briefly at the insert and remove
commands (there isn't much more than what we've seen). We also introduced find and saw
what MongoDB selectors were all about. We've had a good start and laid a solid foundation
for things to come. Believe it or not, you actually know most of what there is to know about
MongoDB - it really is meant to be quick to learn and easy to use. I strongly urge you to play
with your local copy before moving on. Insert different documents, possibly in new collections,
and get familiar with different selectors. Use find, count and remove. After a few tries on
your own, things that might have seemed awkward at first will hopefully fall into place.

10

Chapter 2 - Updating
In chapter 1 we introduced three of the four CRUD (create, read, update and delete) oper-
ations. This chapter is dedicated to the one we skipped over: update. Update has a few
surprising behaviors, which is why we dedicate a chapter to it.

Update: Replace Versus $set
In its simplest form, update takes 2 arguments: the selector (where) to use and what field to
update with. If Roooooodles had gained a bit of weight, we could execute:

db.unicorns.update({name: 'Roooooodles'}, {weight: 590})

(if you've played with your unicorns collection and it doesn't have the original data anymore,
go ahead and remove all documents and re-insert from the code in chapter 1.)

If this was real code, you'd probably update your records by _id, but since I don't know what
_id MongoDB generated for you, we'll stick to names. Now, if we look at the updated record:

db.unicorns.find({name: 'Roooooodles'})

You should discover updates first surprise. No document is found because the second param-
eter we supply is used to replace the original. In other words, the update found a document
by name and replaced the entire document with the new document (the 2nd parameter). This
is different than how SQL's update command works. In some situations, this is ideal and can
be leveraged for some truly dynamic updates. However, when all you want to do is change
the value of one, or a few fields, you are best to use MongoDB's $set modifier:

db.unicorns.update({weight: 590}, {$set: {name: 'Roooooodles', dob: new Date
(1979, 7, 18, 18, 44), loves: ['apple'], gender: 'm', vampires: 99}})

This'll reset the lost fields. It won't overwrite the new weight since we didn't specify it. Now
if we execute:

db.unicorns.find({name: 'Roooooodles'})

We get the expected result. Therefore, the correct way to have updated the weight in the first
place is:

db.unicorns.update({name: 'Roooooodles'}, {$set: {weight: 590}})

Update Modifiers
In addition to $set, we can leverage other modifiers to do some nifty things. All of these
update modifiers work on fields - so your entire document won't be wiped out. For example,
the $inc modifier is used to increment a field by a certain positive or negative amount. For
example, if Pilot was incorrectly awarded a couple vampire kills, we could correct the mistake
by executing:

11

db.unicorns.update({name: 'Pilot'}, {$inc: {vampires: -2}})

If Aurora suddenly developed a sweet tooth, we could add a value to her loves field via the
$push modifier:

db.unicorns.update({name: 'Aurora'}, {$push: {loves: 'sugar'}})

The Updating section of the MongoDB website has more information on the other available
update modifiers.

Upserts
One of updates more pleasant surprises is that it fully supports upserts. An upsert updates
the document if found or inserts it if not. Upserts are handy to have in certain situations and,
when you run into one, you'll know it. To enable upserting we set a third parameter to true.

A mundane example is a hit counter for a website. If we wanted to keep an aggregate count
in real time, we'd have to see if the record already existed for the page, and based on that
decide to run an update or insert. With the third parameter omitted (or set to false), executing
the following won't do anything:

db.hits.update({page: 'unicorns'}, {$inc: {hits: 1}});
db.hits.find();

However, if we enable upserts, the results are quite different:

db.hits.update({page: 'unicorns'}, {$inc: {hits: 1}}, true);
db.hits.find();

Since no documents exists with a field page equal to unicorns, a new document is inserted.
If we execute it a second time,the existing document is updated and hits is incremented to
2.

db.hits.update({page: 'unicorns'}, {$inc: {hits: 1}}, true);
db.hits.find();

Multiple Updates
The final surprise update has to offer is that, by default, it'll update a single document. So far,
for the examples we've looked at, this might seem logical. However, if you executed something
like:

db.unicorns.update({}, {$set: {vaccinated: true }});
db.unicorns.find({vaccinated: true});

You'd likely expect to find all of your precious unicorns to be vaccinated. To get the behavior
you desire, a fourth parameter must be set to true:

12

db.unicorns.update({}, {$set: {vaccinated: true }}, false, true);
db.unicorns.find({vaccinated: true});

In This Chapter
This chapter concluded our introduction to the basic CRUD operations available against a col-
lection. We looked at update in detail and observed three interesting behaviors. First, unlike
an SQL update, MongoDB's update replaces the actual document. Because of this the $set
modifier is quite useful. Secondly, update supports an intuitive upsert which is particularly
useful when paired with the $inc modifier. Finally, by default, update only updates the first
found document.

Do remember that we are looking at MongoDB from the point of view of its shell. The driver
and library you use could alter these default behaviors or expose a different API. For example,
the Ruby driver merges the last two parameters into a single hash: {:upsert => false, :
multi => false}.

13

Chapter 3 - Mastering Find
Chapter 1 provided a superficial look at the find command. There's more to find than un-
derstanding selectors though. We already mentioned that the result from find is a cursor.
We'll now look at exactly what this means in more detail.

Field Selection
Before we jump into cursors, you should know that find takes a second optional parameter.
This parameter is the list of fields we want to retrieve. For example, we can get all of the
unicorns names by executing:
db.unicorns.find(null, {name: 1});

By default, the _id field is always returned. We can explicitly exclude it by specifying {name
:1, _id: 0}.

Aside from the _id field, you cannot mix and match inclusion and exclusion. If you think about
it, that actually makes sense. You either want to select or exclude one or more fields explicitly.

Ordering
A few times now I've mentioned that find returns a cursor whose execution is delayed until
needed. However, what you've no doubt observed from the shell is that find executes imme-
diately. This is a behavior of the shell only. We can observe the true behavior of cursors by
looking at one of the methods we can chain to find. The first that we'll look at is sort. sort
works a lot like the field selection from the previous section. We specify the fields we want to
sort on, using 1 for ascending and --1 for descending. For example:
//heaviest unicorns first
db.unicorns.find().sort({weight: -1})

//by vampire name then vampire kills:
db.unicorns.find().sort({name: 1, vampires: -1})

Like with a relational database, MongoDB can use an index for sorting. We'll look at indexes
in more detail later on. However, you should know that MongoDB limits the size of your sort
without an index. That is, if you try to sort a large result set which can't use an index, you'll
get an error. Some people see this as a limitation. In truth, I wish more databases had the
capability to refuse to run unoptimized queries. (I won't turn every MongoDB drawback into
a positive, but I've seen enough poorly optimized databases that I sincerely wish they had a
strict-mode.)

Paging
Paging results can be accomplished via the limit and skip cursor methods. To get the second
and third heaviest unicorn, we could do:
db.unicorns.find().sort({weight: -1}).limit(2).skip(1)

14

Using limit in conjunction with sort, is a good way to avoid running into problems when
sorting on non-indexed fields.

Count
The shell makes it possible to execute a count directly on a collection, such as:

db.unicorns.count({vampires: {$gt: 50}})

In reality, count is actually a cursor method, the shell simply provides a shortcut. Drivers
which don't provide such a shortcut need to be executed like this (which will also work in the
shell):

db.unicorns.find({vampires: {$gt: 50}}).count()

In This Chapter
Using find and cursors is a straightforward proposition. There are a few additional commands
that we'll either cover in later chapters or which only serve edge cases, but, by now, you should
be getting pretty comfortable working in the mongo shell and understanding the fundamentals
of MongoDB.

15

Chapter 4 - Data Modeling
Let's shift gears and have a more abstract conversation about MongoDB. Explaining a few new
terms and some new syntax is a trivial task. Having a conversation about modeling with a
new paradigm isn't as easy. The truth is that most of us are still finding out what works and
what doesn't when it comes to modeling with these new technologies. It's a conversation we
can start having, but ultimately you'll have to practice and learn on real code.

Compared to most NoSQL solutions, document-oriented databases are probably the least dif-
ferent, compared to relational databases, when it comes to modeling. The differences which
exist are subtle but that doesn't mean they aren't important.

No Joins
The first and most fundamental difference that you'll need to get comfortable with is MongoDB's
lack of joins. I don't know the specific reason why some type of join syntax isn't supported in
MongoDB, but I do know that joins are generally seen as non-scalable. That is, once you start
to horizontally split your data, you end up performing your joins on the client (the application
server) anyways. Regardless of the reasons, the fact remains that data is relational, and
MongoDB doesn't support joins.

Without knowing anything else, to live in a join-less world, we have to do joins ourselves within
our application's code. Essentially we need to issue a second query to find the relevant data.
Setting our data up isn't any different than declaring a foreign key in a relational database.
Let's give a little less focus to our beautiful unicorns and a bit more time to our employees.
The first thing we'll do is create an employee (I'm providing an explicit _id so that we can
build coherent examples)

db.employees.insert({_id: ObjectId("4d85c7039ab0fd70a117d730"), name: 'Leto'})

Now let's add a couple employees and set their manager as Leto:

db.employees.insert({_id: ObjectId("4d85c7039ab0fd70a117d731"), name: 'Duncan'
, manager: ObjectId("4d85c7039ab0fd70a117d730")});
db.employees.insert({_id: ObjectId("4d85c7039ab0fd70a117d732"), name: 'Moneo',
manager: ObjectId("4d85c7039ab0fd70a117d730")});

(It's worth repeating that the _id can be any any unique value. Since you'd likely use an
ObjectId in real life, we'll use them here as well.)

Of course, to find all of Leto's employees, one simply executes:

db.employees.find({manager: ObjectId("4d85c7039ab0fd70a117d730")})

There's nothing magical here. In the worst cases, most of the time, the lack of join will merely
require an extra query (likely indexed).

16

Arrays and Embedded Documents
Just because MongoDB doesn't have joins doesn't mean it doesn't have a few tricks up its
sleeve. Remember when we quickly saw that MongoDB supports arrays as first class objects
of a document? It turns out that this is incredibly handy when dealing with many-to-one or
many-to-many relationships. As a simple example, if an employee could have two managers,
we could simply store these in an array:
db.employees.insert({_id: ObjectId("4d85c7039ab0fd70a117d733"), name: 'Siona',
manager: [ObjectId("4d85c7039ab0fd70a117d730"), ObjectId("4
d85c7039ab0fd70a117d732")] })

Of particular interest is that, for some documents, manager can be a scalar value, while for
others it can be an array. Our original find query will work for both:
db.employees.find({manager: ObjectId("4d85c7039ab0fd70a117d730")})

You'll quickly find that arrays of values are much more convenient to deal with than many-to-
many join-tables.

Besides arrays, MongoDB also supports embedded documents. Go ahead and try inserting a
document with a nested document, such as:
db.employees.insert({_id: ObjectId("4d85c7039ab0fd70a117d734"), name: 'Ghanima
', family: {mother: 'Chani', father: 'Paul', brother: ObjectId("4
d85c7039ab0fd70a117d730")}})

In case you are wondering, embedded documents can be queried using a dot-notation:
db.employees.find({'family.mother': 'Chani'})

We'll briefly talk about where embedded documents fit and how you should use them.

DBRef
MongoDB supports something known as DBRef which is a convention many drivers support.
When a driver encounters a DBRef it can automatically pull the referenced document. A DBRef
includes the collection and id of the referenced document. It generally serves a pretty specific
purpose: when documents from the same collection might reference documents from a differ-
ent collection from each other. That is, the DBRef for document1 might point to a document
in managers whereas the DBRef for document2 might point to a document in employees.

Denormalization
Yet another alternative to using joins is to denormalize your data. Historically, denormalization
was reserved for performance-sensitive code, or when data should be snapshotted (like in an
audit log). However, with the ever-growing popularity of NoSQL, many of which don't have
joins, denormalization as part of normal modeling is becoming increasingly common. This

17

doesn't mean you should duplicate every piece of information in every document. However,
rather than letting fear of duplicate data drive your design decisions, consider modeling your
data based on what information belongs to what document.

For example, say you are writing a forum application. The traditional way to associate a specific
user with a post is via a userid column within posts. With such a model, you can't display
posts without retrieving (joining to) users. A possible alternative is simply to store the name
as well as the userid with each post. You could even do so with an embedded document,
like user: {id: ObjectId('Something'), name: 'Leto'}. Yes, if you let users change their
name, you'll have to update each document (which is 1 extra query).

Adjusting to this kind of approach won't come easy to some. In a lot of cases it won't even
make sense to do this. Don't be afraid to experiment with this approach though. It's not only
suitable in some circumstances, but it can also be the right way to do it.

Which Should You Choose?
Arrays of ids are always a useful strategy when dealing with one-to-many or many-to-many
scenarios. It's probably safe to say that DBRef aren't use very often, though you can certainly
experiment and play with them. That generally leaves new developers unsure about using
embedded documents versus doing manual referencing.

First, you should know that an individual document is currently limited to 4 megabytes in size.
Knowing that documents have a size limit, though quite generous, gives you some idea of
how they are intended to be used. At this point, it seems like most developers lean heavily
on manual references for most of their relationships. Embedded documents are frequently
leveraged, but mostly for small pieces of data which we want to always pull with the parent
document. A real world example I've used is to store an accounts document with each user,
something like:

db.users.insert({name: 'leto', email: 'leto@dune.gov', account: {
allowed_gholas: 5, spice_ration: 10}})

Few or Many Collections
Given that collections don't enforce any schema, it's entirely possible to build a system using a
single collection with a mismatch of documents. From what I've seen, most MongoDB systems
are laid out similarly to what you'd find in a relational system. In other words, if it would be a
table in a relational database, it'll likely be a collection in MongoDB (many-to-many join tables
being an important exception).

The conversation gets even more interesting when you consider embedded documents. The
example that frequently comes up is a blog. Should you have a posts collection and a comments
collection, or should each post have an array of comments embedded within it. Setting aside
the 4MB limit for the time being (all of Hamlet is less than 200KB, just how popular is your

18

blog?), most developers still prefer to separate things out. It's simply cleaner and more ex-
plicit.

There's no hard rule (well, aside from 4MB). Play with different approaches and you'll get a
sense of what does and does not feel right.

In This Chapter
Our goal in this chapter was to provide some helpful guidelines for modeling your data in
MongoDB. A starting point if you will. Modeling in a document-oriented system is different,
but not too different than a relational world. You have a bit more flexibility and one constraint,
but for a new system, things tend to fit quite nicely. The only way you can go wrong is by not
trying.

19

Chapter 5 - When To Use MongoDB
By now you should have a good enough understanding of MongoDB to have a feel for where
and how it might fit into your existing system. There are enough new and competing storage
technologies that it's easy to get overwhelmed by all of the choices.

For me, the most important lesson, which has nothing to do with MongoDB, is that you no
longer have to rely on a single solution for dealing with your data. No doubt, a single solution
has obvious advantages and for a lot projects, possibly even most, a single solution is the
sensible approach. The idea isn't that you must use different technologies, but rather that you
can. Only you know whether the benefits of introducing a new solution outweigh the costs.

With that said, I'm hopeful that what you've seen so far has made you see MongoDB as a
general solution. It's been mentioned a couple times that document-oriented databases share
a lot in common with relational databases. Therefore, rather than tiptoeing around it, let's
simply state that MongoDB should be seen as a direct alternative to relational databases.
Where one might see Lucene as enhancing a relational database with full text indexing, or
Redis as a persistent key-value store, MongoDB is a central repository for your data.

Notice that I didn't call MongoDB a replacement for relational databases, but rather an alter-
native. It's a tool that can do what a lot of other tools can do. Some of it MongoDB does
better, some of it MongoDB does worse. Let's dissect things a little further.

Schema-less
An oft-touted benefit of document-oriented database is that they are schema-less. This makes
them much more flexible than traditional database tables. I agree that schema-less is a nice
feature, but not for the main reason most people mention.

People talk about schema-less as though you'll suddenly start storing a crazy mismatch of
data. There are domains and data sets which can really be a pain to model using relational
databases, but I see those as edge cases. Schema-less is cool, but most of your data is going
to be highly structured. It's true that having an occasional mismatch can be handy, especially
when you introduce new features, but in reality it's nothing a nullable column probably wouldn't
solve just as well.

For me, the real benefit of schema-less design is the lack of setup and the reduced friction
with OOP. This is particularly true when you're working with a static language. I've worked
with MongoDB in both C# and Ruby, and the difference is striking. Ruby's dynamism and its
popular ActiveRecord implementations already reduce much of the object-relational impedance
mismatch. That isn't to say MongoDB isn't a good match for Ruby, it really is. Rather, I think
most Ruby developers would see MongoDB as an incremental improvement, whereas C# or
Java developers would see a fundamental shift in how they interact with their data.

Think about it from the perspective of a driver developer. You want to save an object? Serialize
it to JSON (technically BSON, but close enough) and send it to MongoDB. There is no property

20

mapping or type mapping. This straightforwardness definitely flows to you, the end developer.

Writes
One area where MongoDB can fit a specialized role is in logging. Inserting into MongoDB
is, by default, asynchronous. Writes in MongoDB are already quite fast, and making them
asynchronous just makes them that much faster. In addition, log data is one of those data sets
which can often take advantage of schema-less collections. Finally, MongoDB has something
called a capped collection. So far, all of the implicitly created collections we've created are just
normal collection. We can create a capped collection by using the the db.createCollection
command and flagging it as capped:

//limit our capped collection to 1 megabyte
db.createCollection('logs', {capped: true, size: 1048576})

When our capped collection reaches its 1MB limit, old documents are automatically purged.
A limit on the number of documents, rather than the size, can be set using max. Capped
collections have some interesting properties. For example, you can update a document but it
can't grow in size. Also, the insertion order is preserved, so you don't need to add an extra
index to get proper time-based sorting.

This is a good place to point out that if you don't want your writes to be asynchronous you
simply issue a follow-up command: db.getLastError(). Most drivers encapsulate this as a
safe write, say by specifying {:safe => true} as a second parameter to insert.

Durability
Prior to version 1.8, MongoDB didn't have single-server durability. That is, a server crash
would likely result in lost data. The solution had always been to run MongoDB in a multi-
server setup (MongoDB supports replication). One of the major features added to 1.8 was
journaling. To enable it add a new line with journal=true to the mongodb.config file we
created when we first setup MongoDB (and restart your server if you want it enabled right
away). You probably want journaling enabled (it'll be a default in a future release). Although,
in some circumstances the extra throughput you get from disabling journaling might be a risk
you are willing to take. (It's worth pointing out that some type of applications can easily afford
to lose data).

Durability is only mentioned here because a lot has been made around MongoDB's lack of
single-server durability. This'll likely show up in Google searches for some time to come.
Information you find about this missing feature is simply out of date.

Full Text Search
True full text search capability is something that'll hopefully come to MongoDB in a future
release. With its support for arrays, basic full text search is pretty easy to implement. For
something more powerful, you'll need to rely on a solution such as Lucene/Solr. Of course,
this is also true of many relational databases.

21

Transactions
MongoDB doesn't have transactions. It has two alternatives, one which is great but with limited
use, and the other that is a cumbersome but flexible.

The first is its many atomic operations. These are great, so long as they actually address
your problem. We already saw some of the simpler ones, like $inc and $set. There are also
commands like findAndModify which can update or delete a document and return it atomically.

The second, when atomic operations aren't enough, is to fall back to a two-phase commit. A
two-phase commit is to transactions what manual dereferencing is to joins. It's a storage-
agnostic solution that you do in code. Two-phase commits are actually quite popular in the
relational world as a way to implement transactions across multiple databases. The MongoDB
website has an example illustrating the most common scenario (a transfer of funds). The
general idea is that you store the state of the transaction within the actual document being
updated and go through the init-pending-commit/rollback steps manually.

MongoDB's support for nested documents and schema-less design makes two-phase commits
slightly less painful, but it still isn't a great process, especially when you are just getting started
with it.

Data Processing
MongoDB relies on MapReduce for most data processing jobs. It has some basic aggregation
capabilities, but for anything serious, you'll want to use MapReduce. In the next chapter we'll
look at MapReduce in detail. For now you can think of it as a very powerful and different way
to group by (which is an understatement). One of MapReduce's strength is that it can be
parallelized for working with large sets of data. However, MongoDB's implementation relies
on JavaScript which is single-threaded. The point? For processing of large data, you'll likely
need to rely on something else, such as Hadoop. Thankfully, since the two systems really do
complement each other, there's a MongoDB adapter for Hadoop.

Of course, parallelizing data processing isn't something relational databases excel at either.
There are plans for future versions of MongoDB to be better at handling very large sets of
data.

Tools and Maturity
You probably already know the answer to this, but MongoDB is obviously younger than most
relational database systems. This is absolutely something you should consider. How much
a factor it plays depends on what you are doing and how you are doing it. Nevertheless,
an honest assessment simply can't ignore the fact that MongoDB is younger and the available
tooling around isn't great (although the tooling around a lot of very mature relational databases
is pretty horrible too!). As an example, the lack of support for base--10 floating points will
obviously be a concern (though not necessarily a show-stopper) for systems dealing with
money.

22

On the positive side, drivers exist for a great many languages, the protocol is modern and
simple, and development is happening at blinding speeds. MongoDB is in production at enough
companies that concerns about maturity, while valid, are quickly becoming a thing of the past.

In This Chapter
The message from this chapter is that MongoDB, in most cases, can replace a relational
database. It's much simpler and straightforward; it's faster and generally imposes fewer
restrictions on application developers. The lack of transactions can be a legitimate and serious
concern. However, when people ask where does MongoDB sit with respect to the new data
storage landscape? the answer is simple: right in the middle.

23

Chapter 6 - MapReduce
MapReduce is an approach to data processing which has two significant benefits over more
traditional solutions. The first, and main, reason it was development is performance. In
theory, MapReduce can be parallelized, allowing very large sets of data to be processed across
many cores/CPUs/machines. As we just mentioned, this isn't something MongoDB is currently
able to take advantage of. The second benefit of MapReduce is that you get to write real
code to do your processing. Compared to what you'd be able to do with SQL, MapReduce
code is infinitely richer and lets you push the envelope further before you need to use a more
specialized solution.

MapReduce is a pattern that has grown in popularity, and you can make use of it almost
anywhere; C#, Ruby, Java, Python and so on all have implementations. I want to warn you
that at first this'll seem very different and complicated. Don't get frustrated, take your time
and play with it yourself. This is worth understanding whether you are using MongoDB or not.

A Mix of Theory and Practice
MapReduce is a two-step process. First you map and then you reduce. The mapping step
transforms the inputted documents and emits a key=>value pair (the key and/or value can
be complex). The reduce gets a key and the array of values emitted for that key and produces
the final result. We'll look at each step, and the output of each step.

The example that we'll be using is to generate a report of the number of hits, per day, we
get on a resource (say a webpage). This is the hello world of MapReduce. For our purposes,
we'll rely on a hits collection with two fields: resource and date. Our desired output is a
breakdown by resource, year, month, day and count.

Given the following data in hits:
resource date
index Jan 20 2010 4:30
index Jan 20 2010 5:30
about Jan 20 2010 6:00
index Jan 20 2010 7:00
about Jan 21 2010 8:00
about Jan 21 2010 8:30
index Jan 21 2010 8:30
about Jan 21 2010 9:00
index Jan 21 2010 9:30
index Jan 22 2010 5:00

We'd expect the following output:
resource year month day count
index 2010 1 20 3
about 2010 1 20 1

24

about 2010 1 21 3
index 2010 1 21 2
index 2010 1 22 1

(The nice thing about this type of approach to analytics is that by storing the output, reports
are fast to generate and data growth is controlled (per resource that we track, we'll add at
most 1 document per day.)

For the time being, focus on understanding the concept. At the end of this chapter, sample
data and code will be given for you to try on your own.

The first thing to do is look at the map function. The goal of map is to make it emit a value
which can be reduced. It's possible for map to emit 0 or more times. In our case, it'll always
emit once (which is common). Imagine map as looping through each document in hits. For
each document we want to emit a key with resource, year, month and day, and a simple value
of 1:
function() {
var key = {
resource: this.resource,
year: this.date.getFullYear(),
month: this.date.getMonth(),
day: this.date.getDate()
};
emit(key, {count: 1});
}

this refers to the current document being inspected. Hopefully what'll help make this clear
for you is to see what the output of the mapping step is. Using our above data, the complete
output would be:
{resource: 'index', year: 2010, month: 0, day: 20} => [{count: 1}, {count: 1},
{count:1}]
{resource: 'about', year: 2010, month: 0, day: 20} => [{count: 1}]
{resource: 'about', year: 2010, month: 0, day: 21} => [{count: 1}, {count: 1},
{count:1}]
{resource: 'index', year: 2010, month: 0, day: 21} => [{count: 1}, {count: 1}]
{resource: 'index', year: 2010, month: 0, day: 22} => [{count: 1}]

Understanding this intermediary step is the key to understanding MapReduce. The values from
emit are grouped together, as arrays, by key. .NET and Java developers can think of it as be-
ing of type IDictionary<object, IList<object>> (.NET) or HashMap<Object, ArrayList>
(Java).

Let's change our map function in some contrived way:

25

function() {
var key = {resource: this.resource, year: this.date.getFullYear(), month:
this.date.getMonth(), day: this.date.getDate()};
if (this.resource == 'index' && this.date.getHours() == 4) {
} else {
}
}

The first intermediary output would change to:
{resource: 'index', year: 2010, month: 0, day: 20} => [{count: 5}, {count: 1},
{count:1}]

Notice how each emit generates a new value which is grouped by our key.

The reduce function takes each of these intermediary results and outputs a final result. Here's
what ours looks like:
function(key, values) {
var sum = 0;
values.forEach(function(value) {
sum += value['count'];
});
return {count: sum};
};

Which would output:
{resource: 'index', year: 2010, month: 0, day: 20} => {count: 3}
{resource: 'about', year: 2010, month: 0, day: 20} => {count: 1}
{resource: 'about', year: 2010, month: 0, day: 21} => {count: 3}

Technically, the output in MongoDB is:
_id: {resource: 'home', year: 2010, month: 0, day: 20}, value: {count: 3}

Hopefully you've noticed that this is the final result we were after.

If you've really been paying attention, you might be asking yourself why didn't we simply use
sum = values.length? This would seem like an efficient approach when you are essentially
summing an array of 1s. The fact is that reduce isn't always called with a full and perfect set
of intermediate data. For example, instead of being called with:

26

{resource: 'home', year: 2010, month: 0, day: 20} => [{count: 1}, {count: 1},
{count:1}]

Reduce could be called with:

{resource: 'home', year: 2010, month: 0, day: 20} => [{count: 1}, {count: 1}]
{resource: 'home', year: 2010, month: 0, day: 20} => [{count: 2}, {count: 1}]

The final output is the same (3), the path taken is simply different. As such, reduce must
always be idempotent. That is, calling reduce multiple times should generate the same result
as calling it once.

We aren't going to cover it here but it's common to chain reduce methods when performing
more complex analysis.

Pure Practical
With MongoDB we use the mapReduce command on a collection. mapReduce takes a map
function, a reduce function and an output directive. In our shell we can create and pass a
JavaScript function. From most libraries you supply a string of your functions (which is a bit
ugly). First though, let's create our simple data set:

db.hits.insert({resource: 'index', date: new Date(2010, 0, 20, 4, 30)});
db.hits.insert({resource: 'about', date: new Date(2010, 0, 20, 6, 0)});

Now we can create our map and reduce functions (the MongoDB shell accepts multi-line state-
ments, you'll see … after hitting enter to indicate more text is expected):

var map = function() {
var key = {resource: this.resource, year: this.date.getFullYear(), month:
this.date.getMonth(), day: this.date.getDate()};
};

var reduce = function(key, values) {
var sum = 0;
values.forEach(function(value) {
sum += value['count'];

27

});
return {count: sum};
};

Which we can use the mapReduce command against our hits collection by doing:

db.hits.mapReduce(map, reduce, {out: {inline:1}})

If you run the above, you should see the desired output. Setting out to inline means that
the output from mapReduce is immediately streamed back to us. This is currently limited for
results that are 16 megabytes or less. We could instead specify {out: 'hit_stats'} and
have the results stored in the hit_stats collections:

db.hits.mapReduce(map, reduce, {out: 'hit_stats'});
db.hit_stats.find();

When you do this, any existing data in hit_stats is lost. If we did {out: {merge: 'hit_stats
'}} existing keys would be replaced with the new values and new keys would be inserted as
new documents. Finally, we can out using a reduce function to handle more advanced cases
(such an doing an upsert).

The third parameter takes additional options, for example we could filter, sort and limit the
documents that we want analyzed. We can also supply a finalize method to be applied to
the results after the reduce step.

In This Chapter
This is the first chapter where we covered something truly different. If it made you uncomfort-
able, remember that you can always use MongoDB's other aggregation capabilities for simpler
scenarios. Ultimately though, MapReduce is one of MongoDB's most compelling features. The
key to really understanding how to write your map and reduce functions is to visualize and un-
derstand the way your intermediary data will look coming out of map and heading into reduce.

28

Chapter 7 - Performance and Tools
In this last chapter, we look at a few performance topics as well as some of the tools available
to MongoDB developers. We won't dive deeply into either topic, but we will examine the most
import aspects of each.

Indexes
At the very beginning we saw the special system.indexes collection which contains informa-
tion on all the indexes in our database. Indexes in MongoDB work a lot like indexes in a
relational database: they help improve query and sorting performance. Indexes are created
via ensureIndex:
db.unicorns.ensureIndex({name: 1});

And dropped via dropIndex:
db.unicorns.dropIndex({name: 1});

A unique index can be created by supplying a second parameter and setting unique to true:
db.unicorns.ensureIndex({name: 1}, {unique: true});

Indexes can be created on embedded fields (again, using the dot-notation) and on array fields.
We can also create compound indexes:
db.unicorns.dropIndex({name: 1, vampires: -1});

The order of your index (1 for ascending, --1 for descending) doesn't matter for a single key
index, but it can have an impact for compound indexes when you are sorting or using a range
condition.

The indexes page has additional information on indexes.

Explain
To see whether or not your queries are using an index, you can use the explain method on a
cursor:
db.unicorns.find().explain()

The output tells us that a BasicCursor was used (which means non-indexed), 12 objects were
scanned, how long it took, what index, if any was used as well as a few other pieces of useful
information.

If we change our query to use an index, we'll see that a BtreeCursor was used, as well as the
index used to fulfill the request:
db.unicorns.find({name: 'Pilot'}).explain()

29

Asynchronous Writes
We previously mentioned that, by default, writes in MongoDB are asynchronous. This can
result in some nice performance gains at the risk of losing data during a crash. An interesting
side effect of asynchronous writes is that an error is not returned when an insert/update
violates a unique constraint. In order to be notified about a failed write, one must call db.
getLastError() after an insert. Many drivers abstract this detail away and provide a way to
do a safe write - often via an extra parameter.

Unfortunately, the shell automatically does safe inserts, so we can't easily see this behavior in
action.

Sharding
MongoDB supports auto-sharding. Sharding is an approach to scalability which separates your
data across multiple servers. A naive implementation might put all of the data for users with
a name that starts with A-M on server 1 and the rest on server 2. Thankfully, MongoDB's
sharding capabilities far exceed such a simple algorithm. Sharding is a topic well beyond the
scope of this book, but you should know that it exists and that you should consider it should
your needs grow beyond a single server.

Replication
MongoDB replication works similarly to how relational database replication works. Writes are
sent to a single server, the master, which then synchronizes itself to one or more other servers,
the slaves. You can control whether reads can happen on slaves or not, which can help dis-
tribute your load at the risk of reading slightly stale data. If the master goes down, a slave
can be promoted to act as the new master. Again, MongoDB replication is outside the scope
of this book.

While replication can improve performance (by distributing reads), its main purpose is to
increase reliability. Combining replication with sharding is a common approach. For example,
each shard could be made up of a master and a slave. (Technically you'll also need an arbiter
to help break a tie should two slaves try to become masters. But an arbiter requires very few
resources and can be used for multiple shards.)

Stats
You can obtain statistics on a database by typing db.stats(). Most of the information deals
with the size of your database. You can also get statistics on a collection, say unicorns,
by typing db.unicorns.stats(). Again, most of this information relates to the size of your
collection.

Web Interface
Included in the information displayed on MongoDB's startup was a link to a web-based ad-
ministrative tool (you might still be able to see if if you scroll your command/terminal window
up to the point where you started mongod). You can access this by pointing your browser to

30

http://localhost:28017/. To get the most out of it, you'll want to add rest=true to your
config and restart the mongod process. The web interface gives you a lot of insight into the
current state of your server.

Profiler
You can enable the MongoDB profiler by executing:

db.setProfilingLevel(2);

With it enabled, we can run a command:

db.unicorns.find({weight: {$gt: 600}});

And then examine the profiler:

db.system.profile.find()

The output tells us what was run and when, how many documents were scanned, and how
much data was returned.

You can disable the profiler by calling setProfileLevel again but changing the argument
to 0. Another option is to specify 1 which will only profile queries that take more than 100
milliseconds. Or, you can specify the minimum time, in milliseconds, with a second parameter:

//profile anything that takes more than 1 second
db.setProfilingLevel(1, 1000);

Backups and Restore
Within the MongoDB bin folder is a mongodump executable. Simply executing mongodbump
will connect to localhost and backup all of your databases to a dump subfolder. You can type
mongodump --help to see additional options. Common options are --db DBNAME to back up a
specific database and --collection COLLECTIONAME to back up a specific collection. You can
then use the mongorestore executable, located in the same bin folder, to restore a previously
backup. Again the --db and --collection can be specified to restore on a specific database
and/or collection.

For example, to back up our learn collection to a backup folder, we'd execute (this is its own
executable which you run in a command/terminal window, not within the mongo shell itself):

mongodump --db learn --out backup

To restore only the unicorns collection, we could then do:

mongorestore --collection unicorns backup/learn/unicorns.bson

31

It's worth pointing out that mongoexport and mongoimport are two other executables which
can be used to export and import data from JSON or CSV. For example, we can get a JSON
output by doing:

mongoexport --db learn -collection unicorns

And a CSV output by doing:

mongoexport --db learn -collection unicorns --csv -fields name,weight,vampires

Note that mongoexport and mongoimport cannot always represent your data. Only mongodump
and mongorestore should ever be used for actual backups.

In This Chapter
In this chapter we looked a various commands, tools and performance details of using Mon-
goDB. We haven't touched on everything, but we've looked at the most common ones. In-
dexing in MongoDB is similar to indexing with relational databases, as are many of the tools.
However, with MongoDB, many of these are to the point and simple to use.

32

Conclusion
You should have enough information to start using MongoDB in a real project. There's more
to MongoDB than what we've covered, but your next priority should be putting together what
we've learned, and getting familiar with the driver you'll be using. The MongoDB website has
a lot of useful information. The official MongoDB user group is a great place to ask questions.

NoSQL was born not only out of necessity, but also out of an interest to try new approaches. It
is an acknowledgement that our field is ever advancing and that if we don't try, and sometimes
fail, we can never succeed. This, I think, is a good way to lead our professional lives.

33

Mongodb

More Related Content

What's hot (12)

Viewers also liked (7)

Similar to Mongodb (20)

Recently uploaded (20)

Mongodb