Brad Dayley

NoSQL with
MongoDB

Sams Teach Yourself NoSQL with MongoDB in 24 Hours

Copyright 2015 by Pearson Education

Acquisitions Editor
Mark Taber

All rights reserved. No part of this book shall be reproduced, stored in a retrieval system, or
transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without
written permission from the publisher. No patent liability is assumed with respect to the use of
the information contained herein. Although every precaution has been taken in the preparation of
this book, the publisher and author assume no responsibility for errors or omissions. Nor is any
liability assumed for damages resulting from the use of the information contained herein.

Managing Editor
Kristy Hart

ISBN-13: 9780672337130

Copy Editor
Krista Hansing
Editorial
Services, Inc.

ISBN-10: 0672337134
Library of Congress Control Number: 2014942748
Printed in the United States of America
First Printing: September 2014

Trademarks
All terms mentioned in this book that are known to be trademarks or service marks have been
appropriately capitalized. Pearson cannot attest to the accuracy of this information. Use of a term
in this book should not be regarded as affecting the validity of any trademark or service mark.

Warning and Disclaimer

Every effort has been made to make this book as complete and as accurate as possible, but no
warranty or fitness is implied. The information provided is on an as is basis. The author and the
publisher shall have neither liability nor responsibility to any person or entity with respect to any
loss or damages arising from the information contained in this book or from the use of the CD or
programs accompanying it.

Special Sales
For information about buying this title in bulk quantities, or for special sales opportunities (which
may include electronic versions; custom cover designs; and content particular to your business,
training goals, marketing focus, or branding interests), please contact our corporate sales department at [email protected] or (800) 382-3419.
For government sales inquiries, please contact [email protected].
For questions about sales outside of the U.S., please contact [email protected].

Project Editors
Melissa Schirmer
Elaine Wiley

Indexer
WordWise
Publishing Services
Proofreader
Kathy Ruiz
Technical Editor
Russell Kloepfer
Publishing
Coordinator
Vanessa Evans
Cover Designer
Mark Shirar
Compositor
Gloria Schurick

Contents at a Glance
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Part I: Getting Started with NoSQL and MongoDB

HOUR 1 Introducing NoSQL and MongoDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
HOUR 2 Installing and Configuring MongoDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HOUR 3 Using JavaScript in the MongoDB Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Part II: Implementing NoSQL in MongoDB

HOUR 4 Configuring User Accounts and Access Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
HOUR 5 Managing Databases and Collections from the MongoDB Shell . . . . . . . . . 85
HOUR 6 Finding Documents in the MongoDB Collection from the
MongoDB Shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
HOUR 7 Additional Data-Finding Operations Using the MongoDB Shell . . . . . . . 125
HOUR 8 Manipulating MongoDB Documents in a Collection . . . . . . . . . . . . . . . . . . . . . . . 143
HOUR 9 Utilizing the Power of Grouping, Aggregation, and Map Reduce . . . . . . 167

Part III: Using MongoDB in Applications

HOUR 10 Implementing MongoDB in Java Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
HOUR 11 Accessing Data from MongoDB in Java Applications . . . . . . . . . . . . . . . . . . . . . . 209
HOUR 12 Working with MongoDB Data in Java Applications . . . . . . . . . . . . . . . . . . . . . . . . 231
HOUR 13 Implementing MongoDB in PHP Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
HOUR 14 Accessing Data from MongoDB in PHP Applications. . . . . . . . . . . . . . . . . . . . . . . 273
HOUR 15 Working with MongoDB Data in PHP Applications

........................

293

HOUR 16 Implementing MongoDB in Python Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

HOUR 17 Accessing Data from MongoDB in Python Applications . . . . . . . . . . . . . . . . . . 331
HOUR 18 Working with MongoDB Data in Python Applications . . . . . . . . . . . . . . . . . . . . 349
HOUR 19 Implementing MongoDB in Node.js Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
HOUR 20 Accessing Data from MongoDB in Node.js Applications . . . . . . . . . . . . . . . . . . 391
HOUR 21 Working with MongoDB Data in Node.js Applications . . . . . . . . . . . . . . . . . . . . 411

Part IV: Additional MongoDB Concepts

HOUR 22 Database Administration Using the MongoDB Shell . . . . . . . . . . . . . . . . . . . . . . . 433
HOUR 23 Implementing Replication and Sharding in MongoDB . . . . . . . . . . . . . . . . . . . . 459
HOUR 24 Implementing a MongoDB GridFS Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
How This Book Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Code Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Special Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Q&A, Quiz, and Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Part I: Getting Started with NoSQL and MongoDB

HOUR 1: Introducing NoSQL and MongoDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
What Is NoSQL?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Choosing RDBMS, NoSQL, or Both. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Understanding MongoDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
MongoDB Data Types

..............................................................................

10

Planning Your Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
HOUR 2: Installing and Configuring MongoDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Building the MongoDB Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Accessing the MongoDB HTTP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Accessing MongoDB from the Shell Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Scripting the MongoDB Shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
HOUR 3 : Using JavaScript in the MongoDB Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Defining Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Understanding JavaScript Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Outputting Data in a MongoDB Shell Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Contents

Using Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Implementing Looping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Creating Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Understanding Variable Scope

..................................................................

52

Using JavaScript Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Manipulating Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Working with Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Adding Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Part II: Implementing NoSQL in MongoDB

HOUR 4 : Configuring User Accounts and Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Understanding the Admin Database

..........................................................

69

Administrating User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configuring Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
HOUR 5 : Managing Databases and Collections from the MongoDB Shell . . . . . . . . . . . . 85
Understanding the Database and Collection Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Managing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Managing Collections

..............................................................................

Implementing the Example Dataset

........................................................

96

100

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
HOUR 6 : Finding Documents in the MongoDB Collection from the

MongoDB Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Understanding the Cursor Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Understanding Query Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Getting Documents from a Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

vi

Sams Teach Yourself NoSQL with MongoDB in 24 Hours

Finding Specific Sets of Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
HOUR 7 : Additional Data-Finding Operations Using the MongoDB Shell . . . . . . . . . . . . 125
Counting Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Sorting Results Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Limiting Result Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Finding Distinct Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
HOUR 8 : Manipulating MongoDB Documents in a Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Understanding the Write Concern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Configuring Database Connection Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Getting the Status of Database Write Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Understanding Database Update Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Adding Documents to a Collection in the MongoDB Shell . . . . . . . . . . . . . . . . . . . . . . . . . 149
Updating Documents in a Collection from the MongoDB Shell . . . . . . . . . . . . . . . . . . 151
Saving Documents in a Collection Using the MongoDB Shell . . . . . . . . . . . . . . . . . . . . . 155
Upserting Documents in Collections Using the MongoDB Shell . . . . . . . . . . . . . . . . . . 158
Deleting Documents from a Collection Using the MongoDB Shell

..............

161

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
HOUR 9 : Utilizing the Power of Grouping, Aggregation, and Map Reduce . . . . . . . . . . 167
Grouping Results of Find Operations in the MongoDB Shell . . . . . . . . . . . . . . . . . . . . . . . 167
Using Aggregation to Manipulate the Data During Requests from the
MongoDB Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Applying Map Reduce to Generate New Data Results Using the
MongoDB Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Contents

Part III: Using MongoDB in Applications

HOUR 10 : Implementing MongoDB in Java Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Understanding MongoDB Driver Objects in Java. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Finding Documents Using Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Counting Documents in Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Sorting Results Sets in Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
HOUR 11 : Accessing Data from MongoDB in Java Applications . . . . . . . . . . . . . . . . . . . . . . . . 209
Limiting Result Sets Using Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Finding a Distinct Field Value in Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Grouping Results of Find Operations in Java Applications . . . . . . . . . . . . . . . . . . . . . . . . . 221
Using Aggregation to Manipulate the Data During Requests from Java
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
HOUR 12 : Working with MongoDB Data in Java Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Adding Documents from Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Removing Documents from Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Saving Documents from Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Updating Documents from Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Upserting Documents from Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
HOUR 13 : Implementing MongoDB in PHP Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Understanding MongoDB Driver Objects in PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Finding Documents Using PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Counting Documents in PHP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Sorting Result Sets in PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

vii

viii

Sams Teach Yourself NoSQL with MongoDB in 24 Hours

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
HOUR 14 : Accessing Data from MongoDB in PHP Applications . . . . . . . . . . . . . . . . . . . . . . . . 273
Limiting Result Sets Using PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Finding Distinct Field Values in PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Grouping Results of Find Operations in PHP Applications. . . . . . . . . . . . . . . . . . . . . . . . . . 283
Using Aggregation to Manipulate the Data During Requests from PHP
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
HOUR 15 : Working with MongoDB Data in PHP Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Adding Documents from PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Removing Documents from PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Saving Documents from PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Updating Documents from PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Upserting Documents from PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
HOUR 16 : Implementing MongoDB in Python Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Understanding MongoDB Driver Objects in Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Finding Documents Using Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Counting Documents in Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Sorting Result Sets in Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Contents

ix

HOUR 17 : Accessing Data from MongoDB in Python Applications . . . . . . . . . . . . . . . . . . . . 331

Limiting Result Sets Using Python. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Finding Distinct Field Value in Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Grouping Results of Find Operations in
Python Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Using Aggregation to Manipulate the Data During Requests from Python
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
HOUR 18 : Working with MongoDB Data in Python Applications. . . . . . . . . . . . . . . . . . . . . . . . 349
Adding Documents from Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Removing Documents from Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Saving Documents from Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Updating Documents from Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Upserting Documents from Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
HOUR 19 : Implementing MongoDB in Node.js Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Understanding MongoDB Driver Objects in Node.js

..................................

367

Finding Documents Using Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

Counting Documents in Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Sorting Results Sets in Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
HOUR 20 : Accessing Data from MongoDB in Node.js Applications. . . . . . . . . . . . . . . . . . . . 391
Limiting Result Sets Using Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Finding Distinct Field Value in Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Grouping Results of Find Operations in Node.js Applications . . . . . . . . . . . . . . . . . . . . . 402
Using Aggregation to Manipulate the Data During Requests
from Node.js Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

Sams Teach Yourself NoSQL with MongoDB in 24 Hours

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
HOUR 21 : Working with MongoDB Data in Node.js Applications . . . . . . . . . . . . . . . . . . . . . . . 411
Adding Documents from Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Removing Documents from Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Saving Documents from Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Updating Documents from Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Upserting Documents from Node.js . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Part IV: Additional MongoDB Concepts

HOUR 22 : Database Administration Using the MongoDB Shell . . . . . . . . . . . . . . . . . . . . . . . . . 433
Working with Databases and Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Working with Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Understanding Performance and
Diagnostic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Repairing a MongoDB Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Backing Up MongoDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
HOUR 23 : Implementing Replication and Sharding in MongoDB. . . . . . . . . . . . . . . . . . . . . . . 459
Applying Replication in MongoDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Implementing Sharding in MongoDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

Contents

HOUR 24 : Implementing a MongoDB GridFS Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

Understanding the GridFS Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Implementing a GridFS in the MongoDB Shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Implementing a MongoDB GridFS Using
the Java MongoDB Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Implementing a MongoDB GridFS Using the PHP MongoDB Driver . . . . . . . . . . . . 489
Implementing a MongoDB GridFS Using the Python MongoDB Driver . . . . . . . . 494
Implementing a MongoDB GridFS Using the Node.js MongoDB Driver . . . . . . . 497
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Q&A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Workshop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505

xi

About the Author

Brad Dayley is a senior software engineer with more than 20 years of experience developing enterprise applications. He has designed and developed large-scale business applications, including SAS applications with NoSQL database back ends and rich Internet web
applications as front ends. He is the author of the jQuery and JavaScript Phrasebook, Sams
Teach Yourself jQuery and JavaScript in 24 Hours, and Node.js, MongoDB and AngularJS Web
Development.

Dedication
For D!
A&F

Acknowledgments
Id like to take this page to thank all those who made this title possible. First, I thank my
wonderful wife and boys for giving me the inspiration and support I need. Id never make
it far without you. Thanks to Mark Taber for getting this title rolling in the right direction,
Russell Kloepfer for his technical review, and Melissa Schirmer for managing everything on
the production end.

We Want to Hear from You!

As the reader of this book, you are our most important critic and commentator. We value
your opinion and want to know what were doing right, what we could do better, what areas
youd like to see us publish in, and any other words of wisdom youre willing to pass our
way.
You can email or write to let us know what you did or didnt like about this bookas well
as what we can do to make our books stronger.
Please note that we cannot help you with technical problems related to the topic of this book, and
that due to the high volume of mail we receive, we might not be able to reply to every message.
When you write, please be sure to include this books title, edition number, and author, as
well as your name and contact information.
Email:

[email protected]

Mail:

Sams Publishing
800 East 96th Street
Indianapolis, IN 46240 USA

Reader Services
Visit our website and register this book at informit.com/register for convenient access to
any updates, downloads, or errata that might be available for this book.

Introduction

With billions of people using the Internet today, traditional RDBMS database solutions have difficulty meeting the rapidly growing need to handle large amounts of data. The growing trend is
to introduce specialized databases that are not restricted to the conventions and the legacy overhead of traditional SQL databases. These databases are given the term NoSQL, meaning Not
Only SQL. They are designed not to replace SQL databases, but to provide a different perspective in storing data.
This book teaches you the concepts of NoSQL through the MongoDB perspective. MongoDB is a
NoSQL database that has a reputation for being easy to implement while still robust and scalable. It is currently the most popular NoSQL database in use. MongoDB has matured into a stable platform that several companies have leveraged to provide the data scalability they require.
Each hour in the book provides fundamentals for implementing and using MongoDB as backend storage for high-performing applications. As you complete the 24 one-hour lessons in this
book, you will gain practical understanding of how to build, use, and maintain a MongoDB
database.
So pull up a chair, sit back, and enjoy the process of learning NoSQL through the perspective of
MongoDB development.

How This Book Is Organized

This book is organized into four main parts:
Part I, Getting Started with NoSQL and MongoDB, covers the basic concepts of NoSQL, why
you might want to use it, and available database types. It also covers MongoDB data structures
and design concepts and explores what it takes to get MongoDB installed and running.
Part II, Implementing NoSQL in MongoDB, discusses the fundamental basics for implementing MongoDB. The hours in this part focus on creating databases and collections. They also
cover the different methods of storing, finding, and retrieving data from the MongoDB database.
Part III, Using MongoDB in Applications, introduces you to the MongoDB drivers for some of
the most common programming environments. A MongoDB driver is a library that provides the
necessary tools to programmatically access and use the MongoDB database. This section covers

Introduction

the drivers for Java, PHP, Python, and Node.js. Each programming language section is isolated,
so if you have no interest in a particular language, you can skip its corresponding hour.
Part IV, Additional MongoDB Concepts, rounds out your knowledge of MongoDB by teaching
you additional MongoDB concepts. In this part, you learn some of the basics of administrating
MongoDB databases and look at more advanced MongoDB concepts such as replication, sharding, and GridFS storage.

Code Examples
Two types of code examples appear in this book. The most common are code snippets that
appear in-line with the text to illustrate talking points. Try It Yourself sections also provide code
examples. These examples are more robust and are designed to run as standalone mini applications. To keep the code examples small and easy to follow, they are compressed, with little or no
error checking, for example.
The Try It Yourself examples are presented in listings that include line numbers to make them
easier to follow. They also include a filename in the listing title to indicate which file the listing
came from. If the code listing in the Try It Yourself section has specific output, a follow-up listing
shows you the console output of the code so that you can follow along as you are reading the
book.

Special Elements
As you complete each lesson, margin notes help you immediately apply what you just learned to
your own web pages.
Whenever a new term is used, it is clearly highlightedno flipping back and forth to a glossary.

TIP
Tips and tricks to save you precious time are set aside in Tip boxes so that you can spot them
quickly.

NOTE
Note boxes highlight interesting information you want to be sure not to miss.

CAUTION
When you need to watch out for something, youre warned about it in Caution boxes.

Q&A, Quiz, and Exercises

Q&A, Quiz, and Exercises

Every hour ends with a short question-and-answer session that addresses the kind of dumb
questions all readers wish they dared to ask. A brief but complete quiz lets you test yourself to
be sure you understand everything presented in the hour. Finally, one or two optional exercises
give you a chance to practice your new skills before you move on.

This page intentionally left blank

HOUR 1

Introducing NoSQL and

MongoDB

What Youll Learn in This Hour:

u

How MongoDB structures data

What data types MongoDB supports

When to normalize and denormalize data

How to plan your data model

How capped collections work

When to use indexing, sharding, and replication

How to determine data life cycles

At the core of most large-scale applications and services is a high-performance data storage
solution. The back-end data store is responsible for storing important data such as user account
information, product data, accounting information, and blogs. Good applications require the
capability to store and retrieve data with accuracy, speed, and reliability. Therefore, the data
storage mechanism you choose must be capable of performing at a level that satisfies your
applications demand.
Several data storage solutions are available to store and retrieve the data your applications
need. The three most common are direct file system storage in files, relational databases, and
NoSQL databases. The NoSQL data store chosen for this book is MongoDB because it is the most
widely used and the most versatile.
The following sections describe NoSQL and MongoDB and discuss the design considerations to
review before deciding how to implement the structure of data and the database configuration.
The sections cover the questions to ask and then address the mechanisms built into MongoDB
that satisfy the resulting demands.

HOUR 1: Introducing NoSQL and MongoDB

What Is NoSQL?
A common misconception is that the term NoSQL stands for No SQL. NoSQL actually stands for
Not only SQL, to emphasize the fact that NoSQL databases are an alternative to SQL and can,
in fact, apply SQL-like query concepts.
NoSQL covers any database that is not a traditional relational database management system
(RDBMS). The motivation behind NoSQL is mainly simplified design, horizontal scaling, and
finer control over the availability of data. NoSQL databases are more specialized for types of
data, which makes them more efficient and better performing than RDBMS servers in most
instances.
NoSQL seeks to break away from the traditional structure of relational databases, and enable
developers to implement models in ways that more closely fit the data flow needs of their system.
This means that NoSQL databases can be implemented in ways that traditional relational databases could never be structured.
Several different NoSQL technologies exist, including the HBase column structure, the Redis key/
value structure, and the Virtuoso graph structure. However, this book uses MongoDB and the
document model because of the great flexibility and scalability offered in implementing backend storage for web applications and services. In addition, MongoDB is by far the most popular
and well-supported NoSQL language currently available. The following sections describe some of
the NoSQL database types.

Document Store Databases

Document store databases apply a document-oriented approach to storing data. The idea is
that all the data for a single entity can be stored as a document, and documents can be stored
together in collections.
A document can contain all the necessary information to describe an entity. This includes the
capability to have subdocuments, which in RDBMS are typically stored as an encoded string or
in a separate table. Documents in the collection are accessed via a unique key.

Key-Value Databases
The simplest type of NoSQL database is the key-value stores. These databases store data in a
completely schema-less way, meaning that no defined structure governs what is being stored. A
key can point to any type of data, from an object, to a string value, to a programming language
function.
The advantage of key-value stores is that they are easy to implement and add data to. That
makes them great to implement as simple storage for storing and retrieving data based on a key.
The downside is that you cannot find elements based on the stored values.

Choosing RDBMS, NoSQL, or Both

Column Store Databases

Column store databases store data in columns within a key space. The key space is based on a
unique name, value, and timestamp. This is similar to the key-value databases; however, column store databases are geared toward data that uses a timestamp to differentiate valid content
from stale content. This provides the advantage of applying aging to the data stored in the
database.

Graph Store Databases

Graph store databases are designed for data that can be easily represented as a graph. This
means that elements are interconnected with an undetermined number of relations between
them, as in examples such as family and social relations, airline route topology, or a standard
road map.

Choosing RDBMS, NoSQL, or Both

When investigating NoSQL databases, keep an open mind regarding which database to use and
how to apply it. This is especially true with high-performance systems.
You might need to implement a strategy based on only RDBMS or NoSQLor you might find
that a combination of the two offers the best solution in the end.
With all high-performance databases, you will find yourself trying to balance speed, accuracy,
and reliability. The following is a list of just some considerations when choosing a database:

What does my data look like? Your data might favor a table/row structure of RDBMS, a
document structure, or a simple key-value pair structure.

How is the current data stored? If your data is stored in an RDBMS database, you must
evaluate what it would take to migrate all or part to NoSQL. Also consider whether it
is possible to keep the legacy data as is and move forward with new data in a NoSQL
database.

How important is the guaranteed accuracy of database transactions? A downside of

NoSQL is that most solutions are not as strong in ACID (Atomic, Consistency, Isolation,
Durability) as in the more well-established RDBMS systems.

How important is the speed of the database? If speed is the most critical factor for your
database, NoSQL might fit your data well and can provide a huge performance boost.

What happens when the data is not available? Consider how critical it is for customers when data is not available. Keep in mind that customers view situations in which
your database is too slow to respond as unavailability. Many NoSQL solutions, including
MongoDB, provide a good high availability plan using replication and sharding.

HOUR 1: Introducing NoSQL and MongoDB

How is the database being used? Specifically, consider whether most operations on the
database are writes to store data or whether they are reads. You can also use this exercise
as an opportunity to define the boundaries of how to split up data, enabling you to gear
some data toward writes and other data toward reads.

Should I split up the data to leverage the advantages of both RDBMS and NoSQL?
After you have looked at the previous questions, you might want to consider putting some
of the data, such as critical transactions, in an RDBMS while putting other data, such as
blog posts, in a NoSQL database.

Understanding MongoDB
MongoDB is an agile and scalable NoSQL database. The name Mongo comes from the word
humongous. MongoDB is based on the NoSQL document store model, in which data objects are
stored as separate documents inside a collection instead of in the traditional columns and rows
of a relational database. The documents are stored as binary JSON or BSON objects.
The motivation of the MongoDB language is to implement a data store that provides high performance, high availability, and automatic scaling. MongoDB is extremely simple to install and
implement, as you will see in upcoming hours. MongoDB offers great website back-end storage
for high-traffic websites that need to store data such as user comments, blogs, or other items
because it is fast, scalable, and easy to implement.
The following are some additional reasons MongoDB has become the most popular NoSQL
database:

Document oriented: Because MongoDB is document oriented, the data is stored in the
database in a format that is very close to what you will be dealing with in both server-side
and client-side scripts. This eliminates the need to transfer data from rows to objects and
back.

High performance: MongoDB is one of the highest-performing databases available.

Especially in todays world, where many people interact with websites, having a back end
that can support heavy traffic is important.

High availability: MongoDBs replication model makes it easy to maintain scalability

while keeping high performance and scalability.

High scalability: MongoDBs structure makes it easy to scale horizontally by sharding the
data across multiple servers.

No SQL injection: MongoDB is not susceptible to SQL injection (putting SQL statements
in web forms or other input from the browser that compromises the DB security) because
objects are stored as objects, not by using SQL strings.

Understanding MongoDB

Understanding Collections
MongoDB groups data through collections. A collection is simply a grouping of documents that
have the same or a similar purpose. A collection acts similarly to a table in a traditional SQL
database. However, it has a major difference: In MongoDB, a collection is not enforced by a
strict schema. Instead, documents in a collection can have a slightly different structure from one
another, as needed. This reduces the need to break items in a document into several different
tables, as is often done in SQL implementations.

Understanding Documents
A document is a representation of a single entity of data in the MongoDB database. A collection
consists of one or more related objects. A major difference exists between MongoDB and SQL, in
that documents are different from rows. Row data is flat, with one column for each value in the
row. However, in MongoDB, documents can contain embedded subdocuments, providing a much
closer inherent data model to your applications.
In fact, the records in MongoDB that represent documents are stored as BSON, a lightweight
binary form of JSON. It uses field:value pairs that correspond to JavaScript property:value
pairs that define the values stored in the document. Little translation is necessary to convert
MongoDB records back into JSON strings that you might be using in your application.
For example, a document in MongoDB might be structured similar to the following, with name,
version, languages, admin, and paths fields:
{
name: "New Project",
version: 1,
languages: ["JavaScript", "HTML", "CSS"],
admin: {name: "Brad", password: "****"},
paths: {temp: "/tmp", project:"/opt/project", html: "/opt/project/html"}
}

Notice that the document structure contains fields/properties that are strings, integers, arrays,
and objects, just as in a JavaScript object. Table 11.1 lists the different data types for field values
in the BSON document.
The field names cannot contain null characters, dots (.), or dollar signs ($). In addition, the
_id field name is reserved for the Object ID. The _id field is a unique ID for the system that consists of the following parts:

A 4-byte value representing the seconds since the last epoch

A 3-byte machine identifier

A 2-byte process ID

A 3-byte counter, starting with a random value

10

HOUR 1: Introducing NoSQL and MongoDB

The maximum size of a document in MongoDB is 16MB, to prevent queries that result in an
excessive amount of RAM or intensive hits to the file system. You might never come close to this,
but you still need to keep the maximum document size in mind when designing some complex
data types that contain file data into your system.

MongoDB Data Types

The BSON data format provides several different types used when storing the JavaScript objects
to binary form. These types match the JavaScript type as closely as possible. It is important to
understand these types because you can actually query MongoDB to find objects that have a
specific property with a value of a certain type. For example, you can look for documents in a
database whose timestamp value is a String object or query for ones whose timestamp is a
Date object.
MongoDB assigns each data type of an integer ID number from 1 to 255 when querying by type.
Table 1.1 lists the data types MongoDB supports, along with the number MongoDB uses to identify them.

TABLE 1.1

MongoDB Data Types and Corresponding ID Number

Type

Number

Double

String

Object

Array

Binary data

Object ID

Boolean

Date

Null

10

Regular expression

11

JavaScript

13

Symbol

14

JavaScript (with scope)

15

32-bit integer

16

Timestamp

17

64-bit integer

18

Planning Your Data Model

Type

Number

Min key

255

Max key

127

11

Another point to be aware of when working with the different data types in MongoDB is the
order in which they are compared when querying to find and update data. When comparing
values of different BSON types, MongoDB uses the following comparison order, from lowest to
highest:

1. Min key (internal type)

2. Null
3. Numbers (32-bit integer, 64-bit integer, double)
4. Symbol, String
5. Object
6. Array
7. Binary data
8. Object ID
9. Boolean
10. Date, timestamp
11. Regular expression
12. Max key (internal type)

Planning Your Data Model

Before you begin implementing a MongoDB database, you need to understand the nature of the
data being stored, how that data will be stored, and how it will be accessed. Understanding these
concepts helps you make determinations ahead of time and structure the data and your application for optimal performance.
Specifically, you should ask yourself the following questions:

What basic objects will my application be using?

What is the relationship between the different object typesone-to-one, one-to-many, or

many-to-many?

12

CHAPTER 1: Introducing NoSQL and MongoDB

How often will new objects be added to the database?

How often will objects be deleted from the database?

How often will objects be changed?

How often will objects be accessed?

How will objects be accessedby ID, property values, comparisons, or other?

How will groups of object types be accessedcommon ID, common property value,
or other?

When you have the answers to these questions, you are ready to consider the structure of collections and documents inside MongoDB. The following sections discuss different methods of document, collection, and database modeling you can use in MongoDB to optimize data storage and
access.

Normalizing Data with Document References

Data normalization is the process of organizing documents and collections to minimize redundancy and dependency. This is done by identifying object properties that are subobjects and
that should be stored as a separate document in another collection from the objects document.
Typically, this is useful for objects that have a one-to-many or many-to-many relationship with
subobjects.
The advantage of normalizing data is that the database size will be smaller because only a
single copy of objects will exist in their own collection instead of being duplicated on multiple
objects in single collection. Additionally, if you modify the information in the subobject frequently, then you need to modify only a single instance instead of every record in the objects
collection that has that subobject.
A major disadvantage of normalizing data is that, when looking up user objects that require the
normalized subobject, a separate lookup must occur to link the subobject. This can result in a
significant performance hit if you are accessing the user data frequently.
An example of when normalizing data makes sense is a system that contains users who have
a favorite store. Each User is an object with name, phone, and favoriteStore properties.
The favoriteStore property is also a subobject that contains name, street, city, and zip
properties.
However, thousands of users might have the same favorite store, so you see a high one-to-many
relationship. Therefore, storing the FavoriteStore object data in each User object doesnt
make sense because it would result in thousands of duplications. Instead, the FavoriteStore
object should include an _id object property that can be referenced from documents in the users

Planning Your Data Model

13

stores collection. The application can then use the reference ID favoriteStore to link data
from the Users collection to FavoriteStore documents in the FavoriteStores collection.
Figure 1.1 illustrates the structure of the Users and FavoriteStores collections just described.

Server

Browser
JavaScript
Client Side
JSON/XML/
etc.

JS
JPG

HTTP GET/PUT/AJAX
HTML

User

HTML/
CSS/
Images

JSON
CSS

Webserver
Apache/IIS/
etc.

Other
Services

Server-Side
Scripts
PHP/Java/.NET/
C++/etc.

User
Interactions
Files

DB
MySQL
Oracle
etc.

FIGURE 1.1
Defining normalized MongoDB documents by adding a reference to documents in another collection.

Denormalizing Data with Embedded Documents

Denormalizing data is the process of identifying subobjects of a main object that should be
embedded directly into the document of the main object. Typically, this is done on objects
that have mostly one-to-one relationships or that are relatively small and do not get updated
frequently.
The major advantage of denormalized documents is that you can get the full object back in a
single lookup without needing to do additional lookups to combine subobjects from other collections. This is a major performance enhancement. The downside is that, for subobjects with a
one-to-many relationship, you are storing a separate copy in each document; this slows insertion
a bit and takes up additional disk space.
An example of when normalizing data makes sense is a system that contains users home and
work contact information. The user is an object represented by a User document with name,
home, and work properties. The home and work properties are subobjects that contain phone,
street, city, and zip properties.
The home and work properties do not change often for the user. Multiple users might reside in
the same home, but this likely will be a small number. In addition, the actual values inside the
subobjects are not that big and will not change often. Therefore, storing the home contact information directly in the User object makes sense.

14

CHAPTER 1: Introducing NoSQL and MongoDB

The work property takes a bit more thinking. How many people are you really going to get who
have the same work contact information? If the answer is not many, the work object should be
embedded with the User object. How often are you querying the User and need the work contact information? If you will do so rarely, you might want to normalize work into its own collection. However, if you will do so frequently or always, you will likely want to embed work with
the User object.
Figure 1.2 illustrates the structure of Users with the home and work contact information embedded, as described previously.

Browser
AngularJS
JavaScript
Client Side

Server

HTML
CSS

JSON/XML/
etc.

User

Node.js

HTTP GET/PUT/AJAX

HTML/
CSS/
Images

MongoDB

JSON
JPG

JS

User
Interactions

Express
Webserver

ServerSide
Scripts

Other
Services
Files

FIGURE 1.2
Defining denormalized MongoDB documents by implementing embedded objects inside a document.

Using Capped Collections

A great feature of MongoDB is the capability to create a capped collection. A capped collection is
a collection that has a fixed size. When a new document needs to be written to a collection that
exceeds the size of the collection, the oldest document in the collection is deleted and the new
document is inserted. Capped collections work great for objects that have a high rate of insertion, retrieval, and deletion.
The following list highlights the benefits of using capped collections:

Capped collections guarantee that the insert order is preserved. Queries do not need to
use an index to return documents in the order they were stored, eliminating the indexing
overhead.

Planning Your Data Model

15

Capped collections guarantee that the insertion order is identical to the order on disk by
prohibiting updates that increase the document size. This eliminates the overhead of relocating and managing the new location of documents.

Capped collections automatically remove the oldest documents in the collection. Therefore,
you do not need to implement deletion in your application code.

Capped collections do impose the following restrictions:

You cannot update documents to a larger size after they have been inserted into the
capped collection. You can update them, but the data must be the same size or smaller.

You cannot delete documents from a capped collection. The data will take up space on
disk even if it is not being used. You can explicitly drop the capped collection, which effectively deletes all entries, but you also need to re-create it to use it again.

A great use of capped collections is as a rolling log of transactions in your system. You can
always access the last X number of log entries without needing to explicitly clean up the oldest.

Understanding Atomic Write Operations

Write operations are atomic at the document level in MongoDB. Thus, only one process can be
updating a single document or a single collection at the same time. This means that writing to
documents that are denormalized is atomic. However, writing to documents that are normalized
requires separate write operations to subobjects in other collections; therefore, the write of the
normalized object might not be atomic as a whole.
You need to keep atomic writes in mind when designing your documents and collections to
ensure that the design fits the needs of the application. In other words, if you absolutely must
write all parts of an object as a whole in an atomic manner, you need to design the object in a
denormalized way.

Considering Document Growth

When you update a document, you must consider what effect the new data will have on document growth. MongoDB provides some padding in documents to allow for typical growth during
an update operation. However, if the update causes the document to grow to a size that exceeds
the allocated space on disk, MongoDB must relocate that document to a new location on the
disk, incurring a performance hit on the system. Frequent document relocation also can lead to
disk fragmentation issues. For example, if a document contains an array and you add enough
elements to the array to exceed the space allocated, the object needs to be moved to a new location on disk.

16

CHAPTER 1: Introducing NoSQL and MongoDB

One way to mitigate document growth is to use normalized objects for properties that can grow
frequently. For example instead of using an array to store items in a Cart object, you could create a collection for CartItems; then you could store new items that get placed in the cart as new
documents in the CartItems collection and reference the users cart item within them.

Identifying Indexing, Sharding, and Replication

Opportunities
MongoDB provides several mechanisms to optimize performance, scale, and reliability. As you
are contemplating your database design, consider the following options:

Indexing: Indexes improve performance for frequent queries by building a lookup index
that can be easily sorted. The _id property of a collection is automatically indexed on
because looking up items by ID is common practice. However, you also need to consider
other ways users access data and implement indexes that enhance those lookup methods
as well.

Sharding: Sharding is the process of slicing up large collections of data among multiple
MongoDB servers in a cluster. Each MongoDB server is considered a shard. This provides
the benefit of utilizing multiple servers to support a high number of requests to a large system. This approach provides horizontal scaling to your database. You should look at the
size of your data and the amount of request that will be accessing it to determine whether
to shard your collections and how much to do so.

Replication: Replication is the process of duplicating data on multiple MongoDB instances

in a cluster. When considering the reliability aspect of your database, you should implement replication to ensure that a backup copy of critical data is always readily available.

Large Collections vs. Large Numbers of Collections

Another important consideration when designing your MongoDB documents and collections is
the number of collections the design will result in. Having a large number of collections doesnt
result in a significant performance hit, but having many items in the same collection does.
Consider ways to break up your larger collections into more consumable chunks.
An example of this is storing a history of user transactions in the database for past purchases.
You recognize that, for these completed purchases, you will never need to look them up together
for multiple users. You need them available only for users to look at their own history. If you
have thousands of users who have a lot of transactions, storing those histories in a separate collection for each user makes sense.

Summary

17

Deciding on Data Life Cycles

One of the most commonly overlooked aspects of database design is the data life cycle. How long
should documents exist in a specific collection? Some collections have documents that should be
kept indefinitely (for example, active user accounts). However, keep in mind that each document
in the system incurs a performance hit when querying a collection. You should define a Time To
Live (TTL) value for documents in each of your collections.
You can implement a TTL mechanism in MongoDB in several ways. One method is to implement code in your application to monitor and clean up old data. Another method is to utilize
the MongoDB TTL setting on a collection, to define a profile in which documents are automatically deleted after a certain number of seconds or at a specific clock time.
Another method for keeping collections small when you need only the most recent documents is
to implement a capped collection that automatically keeps the size of the collection small.

Considering Data Usability and Performance

The final point to considerand even reconsideris data usability and performance. Ultimately,
these are the two most important aspects of any web solution and, consequently, the storage
behind it.
Data usability describes the capability of the database to satisfy the functionality of the website.
You need to make certain first that the data can be accessed so that the website functions correctly. Users will not tolerate a website that does not do what they want it to. This also includes
the accuracy of the data.
Then you can consider performance. Your database must deliver the data at a reasonable rate.
You can consult the previous sections when evaluating and designing the performance factors
for your database.
In some more complex circumstances, you might find it necessary to evaluate data usability,
then consider performance, and then look back to usability in a few cycles until you get the balance correct. Also keep in mind that, in todays world, usability requirements can change at any
time. Be sure to design your documents and collections so that they can become more scalable in
the future, if necessary.

Summary
At the core of most large-scale web applications and services is a high-performance data storage solution. The back-end data store is responsible for storing everything from user account
information, to shopping cart items, to blog and comment data. Good web applications require
the capability to store and retrieve data with accuracy, speed, and reliability. Therefore, the data
storage mechanism you choose must perform at a level to satisfy user demand.

18

: Introducing1:NoSQL
CHAPTER
Introducing
and MongoDB
NoSQL and MongoDB

Several data storage solutions are available to store and retrieve data your web applications
need. The three most common are direct file system storage in files, relational databases, and
NoSQL databases. The data store chosen for this book is MongoDB, which is a NoSQL database.
In this hour, you learned about the design considerations to review before deciding how to
implement the structure of data and configuration of a MongoDB database. You also learned
which design questions to ask and then how to explore the mechanisms built into MongoDB to
answer those questions.

Q&A
Q. What types of distributions are available for MongoDB?
A. General distributions for MongoDB support Windows, Linux, Mac OS X, and Solaris.
Enterprise subscriptions also are available for professional and commercial applications
that require enterprise-level capabilities, uptime, and support. If the MongoDB data is
critical to your application and you have a high amount of DB traffic, you might want to
consider the paid subscription route. For information on the subscription, go to
https://www.mongodb.com/products/mongodb-subscriptions.
Q. Does MongoDB have a schema?
A. Sort of. MongoDB implements dynamic schemas, enabling you to create collections without
having to define the structure of the documents. This means you can store documents that
do not have identical fields.

Workshop
The workshop consists of a set of questions and answers designed to solidify your understanding
of the material covered in this hour. Try answering the questions before looking at the answers.

Quiz
1. What is the difference between normalized and denormalized documents?
2. True or false: JavaScript is a supported data type in a MongoDB document.
3. What is the purpose of a capped collection?

Quiz Answers
1. Denormalized documents have subdocuments within them, whereas subdocuments of normalized documents are stored in a separate collection.
2. True.

Workshop

19

3. A capped collection enables you to limit the total size or number of documents that can be
stored in a collection, keeping only the most recent.

Exercises
1. Go to the MongoDB documentation website and browse the FAQ page. This page answers
several questions on a variety of topics that can give you a good jump-start. You can find
the FAQ page at http://docs.mongodb.org/manual/faq/.

This page intentionally left blank

This page intentionally left blank

Index

$lte operator, 110

$sort operator, 147, 172

$lt operator, 110

$strcasecmp operator, 175

!== (both value and type are not

equal) operator, 42

$match operator, 172

$substr operator, 175

$max operator, 173

$subtract operator, 175

!= (is not equal) operator, 42

$min operator, 173

$sum operator, 173

! (not) operator, 42

$mod operator, 110, 175

$toLower operator, 175

$add operator, 175

$multiply operator, 175

$toUpper operator, 175

$addToSet operator, 147, 173

$ne operator, 110

$type operator, 110

$all operator, 110

$nin operator, 110

$unset operator, 147

$and operator, 110

$nor operator, 110

$unwind operator, 172

$avg operator, 173

$not operator, 110

% (modulous) operator, 40

$bit operator, 147

$ operator, 147

&& (and) operator, 42

$concat operator, 175

$or operator, 110

* (multiplication) operator, 40

$divide operator, 175

$pop operator, 147

+ (addition) operator, 40

$each operator, 147

$project operator, 172

++ (increment) operator, 40

$elemMatch operator, 110

$pullAll operator, 147

-- (decrement) operator, 40

$exists operator, 110

$pull operator, 147

- (subtraction) operator, 40

$first operator, 173

$push operator, 147, 173

/ (brackets), 45, 49

$group operator, 172, 287

$regex operator, 110

/ (division) operator, 40

$gte operator, 110

$rename operator, 147

() (parentheses), 50

$gt operator, 110

$setOnInsert operator, 147

< (is less than) operator, 42

$inc operator, 147

$set operator, 147

$in operator, 110

$size operator, 110

<= (is less than or equal to)

operator, 42

$last operator, 173

$skip operator, 172

$limit operator, 172, 287

$slice operator, 147

SYMBOLS

=== (both value and type are

equal) operator, 42

506

== (is equal to) operator

== (is equal to) operator, 42

objects, 12

> (is greater than) operator, 42

PHP applications, 273

files, GridFS Stores, 485,

491, 494, 498

>= (is greater than or equal to)

operator, 42

applying aggregation,
287-290

indexes, 438-440

|| (or) operator, 42

grouping results, 283-287

objects, 12

A
accessing

GridFS Stores, 484

Node.js applications, 498,

500-501
Python, 494, 496-497
HTTP interfaces, 26

addition (+) operator, 40

searching distinct field

values, 281-283

addUser() method, 70, 87,

187, 370

applying aggregation,
344-347

documents, counting,
125-127

files, 492-493

limiting result sets,

273-281

Python application, 331

access control, configuring,

78-82

overview of, 69

database administrator,
formatting, 79
users

aggregation
applying, 171-178

formatting, 72

operators

managing, 70-78

grouping results, 221-225

adding

Node.js applications, 406-409

expression, 173-175
framework, 174-172
PHP applications, 287-290
pipelines, 176
Python application, 344-347

documents

MongoGridFS objects in
PHP, 490

collections, 149-151, 232

Node.js applications, 391

Node.js applications,
411-416

limiting result sets,

391-399

aggregate() method, 89, 172,

188, 225, 254, 314, 345, 371

Java, 225-228

ACID (Atomic, Consistency,

Isolation, Durability), 7

applying aggregation,
406-409

user accounts, managing,

70-78

administrator, formatting,
78

accuracy, 7, 17

MongoDB shell clients, 27-31

admin database

limiting result sets,

331-338

finding distinct field

values, 218-221

limiting result sets,

209-218

add_user() method, 313

access control, configuring,

78-82

authentication, starting, 79

applying aggregation,
225-228

shards to clusters, 473

grouping results, 341

accounts

Java applications, 209

items to arrays, 63

Java applications, 231-235

PHP applications, 293-297

Python application,
349-353
error handling, 65-67

analyzing queries, 449-451

and (&&) operator, 42
anonymous functions, 51
append() method, 192
applications
Java. See Java applications
Node.js. See Node.js
applications

Collection object

PHP. See PHP applications

strings

Python. See Python

applications

converting, 62
splitting, 58

applying

values, searching documents

based on, 117

aggregation, 171-178
Java, 225-228

assigning

Node.js applications,
406-409

roles, 71

Booleans, 39
both value and type are equal
(===) operator, 42
both value and type are not equal
(!==) operator, 42
brackets (/), 45, 49
BSON (binary JSON), 9

values to variables, 38

PHP applications, 287-290

assignment operators, 41

pipelines, 176

Atomic, Consistency, Isolation,

Durability. See ACID

atomic write operations, 15

callback functions, 368

arrays, 60-65

authenticate() method, 187, 253,

313, 370

capped collections, formatting,

14-15, 436-437

if statements, 43-44

authentication, starting, 79

indexes, 438-443

auth() method, 87

changeUserPassword()
method, 87

replication, 459-467

auth setting, 24

characters, null, 9

Python application,
344-347
anonymous functions, 51

clients, shells

results, mapReduce() method,

178-183
arbiter servers, 460
arithmetic operators, 40-41
Array objects, PHP applications,
257
arrays, 39
applying, 60-65
combining, 62
fields

accessing MongoDB from,

27-31

scripting, 33-34

background property, 440

cloneCollection() method, 87

backing up

cloneDatabase() method, 87

databases, 454-455
MongoDB, 454-455
BasicDBObject object, Java
applications, 191-194

close() method, 186, 191, 252,

312, 368
clusterAdmin role, 71
privileges, 91
clusters, sharding

contents, 118

batchInsert() method, 254, 294

searching documents
based on, 118

batchSize() method, 108, 188,

256, 373

adding, 473

batch_size() method, 316

formatting, 475-479

items

507

deploying, 472

adding/deleting, 63

binary JSON. See BSON

code property, 145

searching, 63

bind_ip setting, 24

collection_names() method, 313

blocks

Collection object, 89

iterating through, 62
manipulating, 61

finally, 66

Node.js applications, 370-371

try/catch, 65

Python application, 313

How can we make this index more useful? Email us at [email protected]

508

collections

collections, 9
capped, formatting, 14-15,
436-437
databases, managing,
433-437

combining

consoles, starting shells, 28

arrays, 62

constructors, shells, 29

strings, 58

contents, searching, 118

command-line parameters, 22-23

commands

converting
arrays into strings, 62

deleting, 98-100

<database>, 87

design, 16

getLastError, 144-145

copy() method, 191

documents. See also

documents

mongofiles, 482-483

copyDatabase() method, 87

parameters, 30-31

copying databases, 434-435

shells, 28, 32-33

copyTo() method, 89

top, 451-453

count() method, 89, 108, 126,

188, 202, 254, 256, 265, 314,
316, 324, 371, 373, 383

adding, 149-151, 232

configuring write concerns,
143-144
database update
operators, 146-147
deleting, 161-163, 236
error handling, 144
manipulating, 143
paging, 136
PHP applications, 294
retrieving, 112-116
saving, 155-158, 239
status of database write
requests, 145
updating, 151-155, 243
upserting, 158-160, 246
formatting, 96-98
lists, viewing, 96
managing, 96
reindexing, 441-443
renaming, 435-436
sharding, enabling, 474
statistics, viewing, 443-444
users, counting documents,
126
collections() method, 370
column store databases, 7

use <new_database_name>,
92
comparison operators, 42

records, 9

counting documents, 125-127

compound indexes, 439

Java applications, 201-203

cond parameter, 168

Node.js applications, 383-385

config servers, 470, 472

PHP applications, 265-267

configuring

Python application, 324-326

access control, 78-82

countWords() method, 202

databases, 22

create_collection() method, 313

error handling, 144

createCollection() method, 87, 97,

187, 253, 370

MongoDB, 23-26
PHP application write
concerns, 257

createIndex() method, 89

servers, 461

Cursor objects, 107-108

current() method, 256

sharding tag ranges, 475

documents, counting, 126

write concerns, 143-144

Node.js applications, 373

connect() method, 186, 252, 368

Connection objects, overview
of, 86

Python applications, 315,

324, 327, 332
results

connectionId property, 145

limiting, 130-138

connections

sorting, 128-130

databases, configuring error

handling, 144
write concerns, configuring,
143-144

customizing objects, defining,

54-55

diagnostics, managing databases

managing, 91
optimizing, 443-453

data life cycles, 17

repairing, 453-454

DBCursor object, Java

applications, 189-191, 202,
204, 210, 213

modifying, 92

DBObject objects, 191-194

JavaScript, 38-39

profiling, 446-448

declaring variables, 38

MongoDB, 10-11

queries, evaluating, 449-451

decrement (--) operator, 40

results

default_id indexes, 439

data types

<database> command, 87
Database object, 86-87

grouping, 167-171

defining

Node.js applications, 369-370

limiting, 130-138

documents, 13

Python applications, 313

sorting, 128-130

functions, 49

database_names() method, 312

roles, assigning, 71

objects, customizing, 54-55

databases

selecting, 7-8

variables, 37-38

access control, implementing,

80
admin, overview of, 69
administrator accounts,
formatting, 79

sharding, enabling, 474

509

deleting

shells, managing, 433

collections, 98-100

statistics, viewing, 94-96,

443-444

databases, 93-94
documents

testing, 31

collections, 236

backing up, 454-455

top command, 451-453

Java applications, 236-238

Collection object, 89

update operators, 146-147

collections, managing,
433-437

users, listing, 74

Node.js applications,
416-419

validating, 444-446

PHP applications, 297-299

column store, 7

write concerns, configuring,

143-144

Python application,
353-355

Connection objects, overview

of, 86

dataset examples, implementing,

100-103

files, GridFS Stores, 486,

491, 495, 499

connections, configuring error

handling, 144

dataSize() method, 89

indexes, 441

DB object

items from arrays, 63

configuring, 22

copying, 434-435

Java applications, 187

objects, 12

deleting, 93-94

PHP applications, 253

users, 77

document store, 6

db() method, 368

denormalizing data, 13-14

formatting, 92-93

dbAdminAnyDatabase role, 71

deploying

graph store, 7

dbAdmin role, 71

replica sets, 462-463

indexes, 438-443

DBCollection object

sharding clusters, 472

key-value, 6

Java applications, 188

design, 6, 16

lists, viewing, 91

PHP applications, 279

diagnostics, managing databases,

443-453

How can we make this index more useful? Email us at [email protected]

510

Dictionary objects, PHP applications

Dictionary objects, PHP

applications, 317

Java applications

updating, 302-305

adding, 231-235

upserting, 305-308

displayGroup() method, 284

counting, 201-203

Python application, 349

displayWords() method, 131

deleting, 236-238

adding, 349-353

distinct field values

saving, 239-241

counting, 324-326

Node.js applications, 400-402

searching, 194-201

deleting, 353-355

PHP applications, 281-283

sorting results, 203-206

saving, 355-357

Python applications, 339-341

updating, 241-245

searching, 318-324

upserting, 245-249

sorting results, 326-328

searching, 138-140, 218-221

distinct() method, 138, 188, 254,
314, 316, 339, 371

manipulating, 143

updating, 358-361

Node.js applications, 411

upserting, 361-364

distinctField() method, 89

adding, 411-416

division (/) operator, 40

counting, 383-385

references, normalizing data,

12-13

document store databases, 6

deleting, 416-419

results

documents

grouping results, 402-406

collections, 9. See also

collections
adding, 149-151, 232
configuring write concerns,
143-144
database update
operators, 146-147
deleting, 161-163, 236
error handling, 144
retrieving, 112-116
saving, 155-158, 239
status of database write
requests, 145
updating, 151-155, 243
upserting, 158-160, 246
counting, 125-127
Cursor objects, 107-108
distinct field values,
retrieving, 139
embedding, denormalizing
data, 13-14

limiting, 130-138
sorting, 128-130

objects used as, 374

paging, 397

shells, searching in, 112-116

retrieving, 377-383

sizing, 10

saving, 419-423

specific, retrieving (using

PHP), 262-265

searching distinct field

values, 400-402
sorting results, 385-388

specific sets of, searching,

117-122

updating, 423-427

updating, 15

upserting, 427-431

values, searching, 118

overview of, 9-10

do/while loops, 45

parameters, PHP Arrays

objects as, 257

drivers

PHP applications, 293

adding, 293-297
counting, 265-267
deleting, 297-299

Java applications, 185-194

Node.js applications, 367-377
PHP applications, 251-259
drop() method, 89, 188, 254,
314, 371

reviewing, 260-262

drop_collection() method, 313

saving, 299-302

drop_database() method, 312

searching, 259-265

drop_index() method, 314

sorting results, 267-270

dropCollection() method, 370

dropDatabase() method, 87, 93,
186-187

fromdb parameter

dropDups property, 440

find operations
PHP applications, 283-287

dropIndex() method, 89, 188, 254

fault tolerance, 462
fields
addUser() method, 70

511

arrays

embedding documents,
denormalizing data, 13-14
enabling sharding

find() method, 89, 107, 112, 126,

188, 254, 259, 314, 371, 377
fields, limiting, 132
find_and_modify() method, 314

contents, 118

find_one() method, 314

searching documents
based on, 118

findAndModify() method, 89, 188,

254, 371

collections, 474

limiting, 132, 212

finding. See searching

databases, 474

naming, 9

findOne() method, 89, 188, 194,

254, 259, 371

engines, starting/stopping, 22

Node.js applications, 394

ensureIndex() method, 89, 188,

254, 314

parameters, 213

err property, 145

errors
handling
adding, 65-67

PHP applications, limiting,

276

eval() method, 87
evaluating
queries, 449-451
shells, expressions, 31-32
example datasets, implementing,
100-103
executing
shell scripting, 32
variables, 38
exit command, 28

for loops, 45-46

for/in loops, 46-47

values

forEach() method, 108

searching, 117, 138-140,

218-221

formatting. See also design

fields:value operator, 110

capped collections, 14-15,

436-437

files

collections, 96-98

throwing, 66

--eval command-line option, 31-32

results, grouping, 167-171,

221-225

Python applications, limiting,

334

document collections, 144

escape codes, string objects, 56

findone() method, 112

configuration settings, 24

config servers, instances, 472

GridFS Stores

database administrator
accounts, 79

adding, 485, 491, 494,

498
deleting, 486, 491, 495,
499

databases, 92-93
example datasets, 101
functions, 49-52

listing, 485

replica sets, 463-467

manipulating, 492-493

sharding clusters, 475-479

retrieving, 486, 491, 495,

499

users

JavaScript, specifying, 32-33

accounts, 72
administrator accounts, 78

expression operators, aggregation,

173-175

finalize option, 179

finalize parameter, 168

frameworks, aggregation
operators, 174-172

expressions, evaluating shells,

31-32

finally blocks, 66

fromdb parameter, 434

How can we make this index more useful? Email us at [email protected]

512

fromhost parameter

fromhost parameter, 434

greeting() function, 50

functions

GridFS Stores

anonymous, applying, 51
callback, 368
defining, 49
formatting, 49-52
greeting(), 50
print(), 32
values, returning, 50
variables, passing, 50

files

handling errors, 65-67

adding, 485, 491, 494,

498

hashed indexes, 439

deleting, 486, 491, 495,

499

Hello World, 49

manipulating, 492-493
retrieving, 486, 491, 495,
499
implementing, 481
Java, 484-489
Node.js applications

hasNext() method, 108, 191, 256

help <option> command, 28

help() method, 87
high availability, replication, 460
hint() method, 108
horizontal scaling, 6
hostInfo() method, 87
HTTP interfaces, accessing, 26

accessing, 498, 500-501

implementing, 497-501

generating new data results,

178-183
geospatial indexes, 439
getCollection() method, 87, 187
getCollectionNames() method, 96
getConnections() method, 252
getDatabaseNames() method,
186
getDB() method, 86, 186
getIndexes() method, 89
getLastError command, 144-145
getLastError() method, 187
getMongo() method, 87
getName() method, 87
getNext() method, 256
getReadPrefMode() method, 86
getReadPrefTagSet() method, 86
getSiblingDB() method, 87

overview of, 481-482

PHP, 489-493

Python
accessing, 496-497
implementing, 494-497
shells, implementing,
482-484
group() method, 89, 168, 188,
254, 314, 371

if statements, applying, 43-44

implementing, 6
access control, 80
example datasets, 100-103
GridFS Stores, 481
Java, 484-489

objects, 169, 284

Node.js applications,
497-501

results, 167-171, 221-225

PHP, 489-493

grouping

Node.js applications,
402-406
PHP applications, 283-287
Python applications, 341
growth, documents, 15. See also
updating

Python, 494-497
shells, 482-484
in Java applications, 185.
See also Java applications
looping, 44-49
replication, 459

getStats() method, 188

sharding, 459, 468-479

graph store databases, 7

strategies, 7

life cycles, data

switch statements, 44

files, specifying, 32-33

functions, formatting, 49-52

upsert, 158
increment (++) operator, 40
indexes, 16
adding, 438-440
collections, reindexing,
441-443
deleting, 441
indexOf() method, 58
initial parameter, 168
insert() method, 89, 158, 188,
231, 254, 314, 371
inserting, 149. See also adding

operators, 40-44. See also

operators

data access, 209

applying aggregation,
225-228

shells, 30, 40

finding distinct field

values, 218-221

variables

strings, manipulating, 56-60

defining, 37-38

grouping results, 221-225

limiting result sets,
209-218

instances, formatting config

servers, 472

DBCollection object, 188

DBCursor object, 202, 204,
210

HTTP, 26

DBObject objects, 191-194

REST, 26

documents

interrupting loops, 47

adding, 231-235

is equal to (==) operator, 42

counting, 201-203

is greater than (>) operator, 42

deleting, 236-238

is greater than or equal to (>=)

operator, 42

saving, 239-241

is less than (<) operator, 42

sorting results, 203-206

is less than or equal to (<=)

operator, 42

updating, 241-245

scope, 52-53
journal setting, 24
jsMode option, 179

K
key-value databases, 6
keyf parameter, 168
keys
parameters, 168, 434
sharding, selecting, 470-471
values

searching, 194-201

upserting, 245-249

is not equal (!=) operator, 42

driver objects, 185-194

isAuthenticated() method, 187

isCapped() method, 89

GridFS Stores, implementing,

484-489

items, arrays

MongoClient object, 186

searching, 63

objects, 53-56

BasicDBObject object,
191-194

DB object, 187

adding/deleting, 63

looping, implementing, 44-49

Java applications, 185

installing MongoDB, 22

interfaces

513

grouping objects, 169,

284
keywords
function, 49
return, 50
var, 38

results, paging, 215

JavaScript

iterating through arrays, 62

arrays, applying, 60-65

iterator() method, 191

data types, 38-39

lastOp property, 145

error handling, adding, 65-67

life cycles, data, 17

How can we make this index more useful? Email us at [email protected]

514

limiting

limiting
fields, 132, 212
Node.js applications, 394

lookups, denormalized
documents, 13

requests, applying
aggregation, 171-178

looping

results, 181

PHP applications, 276

do/while loops, 45

Python applications, 334

for loops, 45-46

map() method, 108, 131

result sets, 130-138,

209-218

for/in loops, 46-47

mapReduce() method, 89, 188

results

interrupting, 47

max() method, 108

variables, 38

maxConns setting, 24

while loops, 45

methods

Node.js applications,
391-399

implementing, 44-49

PHP applications, 273-281

Python application,
331-338
limit option, 179
limit() method, 108, 130, 136,
191, 210, 216, 256, 274, 316,
332, 373
limitResults() method, 210
listCollections() method, 253
listDBs() method, 252
listing files, GridFS Stores
Java, 485
Node.js applications, 498
PHP, 490-491
Python, 494
lists
collections, viewing, 96
databases, viewing, 91
users, 74
literals, objects, 39
load() method, 32
log [name] : command, 28
logappend setting, 24
logout() method, 87
logpath setting, 24

strings, 56-60

results, applying, 178-183

add_user(), 313
addUser(), 70, 87, 187, 370

aggregate(), 89, 172, 188,

225, 254, 314, 345, 371

main() method, 202

append(), 192

managing

auth(), 87

access control, configuring,

78-82

authenticate(), 187, 253,

313, 370

collections, 96

batch_size(), 316

configuration settings, 23

batchInsert(), 254, 294

databases, 91

batchSize(), 108, 188, 256,

373

collections, 433-437
indexes, 438-443
optimizing, 443-453
repairing, 453-454
shells, 433
user accounts, 70-78
manipulating. See also modifying
arrays, 61
documents, 143
GridFS Stores
files, 492-493
Node.js applications,
500-501
Python, 496-497

changeUserPassword(), 87
cloneCollection(), 87
cloneDatabase(), 87
close(), 186, 191, 252, 312,
368
Collection objects, 89
collection_names(), 313
collections(), 370
connect(), 186, 252, 368
Connection objects, 86
copy(), 191
copyDatabase(), 87
copyTo(), 89

methods

count(), 89, 108, 126, 188,

202, 254, 256, 265, 314,
316, 324, 371, 373, 383

515

find_and_modify(), 314

limitResults(), 210

find_one(), 314

listCollections(), 253

findAndModify(), 89, 188,

254, 371

listDBs(), 252

findOne(), 89, 188, 194, 254,

259, 371

logout(), 87

findone(), 112

map(), 108, 131

createIndex(), 89

forEach(), 108

current(), 256

getCollection(), 87, 187

mapReduce(), 89, 178-183,

188

Cursor object, 108

getCollectionNames(), 96

max(), 108

Database objects, 87

getConnections(), 252

min(), 108

database_names(), 312

getDatabaseNames(), 186

MongoClient object, 186, 252

dataSize(), 89

getDB(), 86, 186

native, shells, 29

DB objects, 187

getIndexes(), 89

new Mongo (), 86

db(), 368

getLastError(), 187

next(), 108, 115, 256

DBCollection objects, 188

getMongo(), 87

objsLeftInBatch(), 108

DBCurosor objects, 191

getName(), 87

open(), 368

displayGroup(), 284

getNext(), 256

partitions, selecting, 471-472

displayWords(), 131

getReadPrefMode(), 86

print(), 40

distinct(), 138, 188, 254,

314, 316, 339, 371

getReadPrefTagSet(), 86

printjson(), 40

getSiblingDB(), 87

push(), 60

distinctField(), 89

getStats(), 188

read_preference(), 312-314

drop(), 89, 188, 254, 314,

371

group(), 89, 168, 188, 254,

314, 371

readPref(), 108

drop_collection(), 313

hasNext(), 108, 191, 256

drop_database(), 312

help(), 87

remove(), 89, 161, 188, 236,

254, 297, 314, 371

drop_index(), 314

hint(), 108

remove_user(), 313

dropCollection(), 370

hostInfo(), 87

removeUser(), 87, 187, 370

dropDatabase(), 87, 93,

186-187

indexOf(), 58

rename(), 314, 371

dropIndex(), 89, 188, 254

insert(), 89, 158, 188, 231,

254, 314, 371

renameCollection(), 89

ensureIndex(), 89, 188, 254,

314

isAuthenticated(), 187

countWords(), 202
create_collection(), 313
createCollection(), 87, 97,
187, 253, 370

eval(), 87
find(), 89, 107, 112, 126,
188, 254, 259, 314, 371,
377

isCapped(), 89
iterator(), 191
limit(), 108, 130, 136, 191,
210, 216, 256, 274, 316,
332, 373

load(), 32

main(), 202

reIndex(), 89

repairDatabase(), 87
resetDoc(), 242
runCommand(), 87, 144
save(), 89, 155, 188, 239,
254, 299, 314, 371

How can we make this index more useful? Email us at [email protected]

516

methods

selectCollection(), 252-253
selectDB(), 252

databases, 92

multiple documents, searching,

115. See also documents

serverStatus(), 87

objects, 12

multiplication (*) operator, 40

setReadPreference(),
186-188, 252-254, 313

modifying

modulous (%) operator, 40

MongoClient object

setReadPrefMode(), 86

Java applications, 186

setSlaveOk(), 86

Node.js applications, 368

setWriteConcern(), 186-188

PHP applications, 252

n property, 145

Python applications, 312

name property, 440

showWord(), 300
shutdownServer(), 87

naming

size(), 108, 191

MongoCollection object, PHP

applications, 253-254

skip(), 108, 136, 191, 216,

256, 316, 373

MongoCursor object, PHP

applications, 256, 274-276

native methods, shells, 29

snapshot(), 108

MongoDB. See also databases

new Mongo () method, 86

sort(), 108, 128, 191, 204,

256, 267, 316, 326, 373,
386
split(), 58

next() method, 108, 115, 256

configuring, 23-26

noauth setting, 24

data types, 10-11

Node.js applications, 367

stats(), 89, 95
storageSize(), 89

installing, 22

String object, manipulating,

56

Java applications. See Java

applications

toArray(), 108, 191, 373

overview of, 8-10

totalIndexSize(), 89

shells

totalSize(), 89

accessing clients, 27-31

update(), 89, 188, 242, 254,

302, 305, 314, 371

scripting, 31-34
starting, 22

validate(), 92

stopping, 25

write_concern(), 312-314

variables, 38

backing up, 454-455

HTTP interfaces,
accessing, 26

version(), 87

fields, 9

MongoDB object, PHP

applications, 253

min() method, 108

mongofiles command, 482-483

models, planning, 11-17

MongoGridFS objects in PHP,

accessing, 490
multikey indexes, 439

Collection object, 370-371

Cursor objects, 373
data access, 391
applying aggregation,
406-409
grouping results, 402-406
limiting result sets,
391-399
Database object, 369-370
documents, 411
adding, 411-416
counting, 383-385
deleting, 416-419
paging, 397
retrieving, 377-383
saving, 419-423
searching distinct field
values, 400-402

operators

sorting results, 385-388

Cursor, 107-108

operators

updating, 423-427

counting documents, 126

$, 148

upserting, 427-431

limiting results, 130-138

$add, 175

sorting results, 128-130

$addToSet, 148, 173

driver objects, 367-377

Database, 86-87

$all, 110

accessing, 498, 500-501

DB, 187

$and, 110

implementing, 497-501

DBCollection, 188

$avg, 173

DBCursor, 189-191, 202,

204, 210

$bit, 148

DBObject, 191-194

$divide, 175

defining, customizing, 54-55

$each, 148

drivers

$elemMatch, 110

GridFS Stores

MongoClient object, 368

objects used as documents/
parameters, 374
specific documents, 380
nohttpinterface setting, 24

$concat, 175

normalizing data, 12-13

Java applications, 185-194

$exists, 110

NoSQL

$first, 173

overview of, 6

Node.js applications,
367-377

selecting, 7-8

PHP applications, 251-259

$gt, 110

$group, 172, 287

not (!) operator, 42

fields, limiting, 132, 212

$gte, 110

null characters, 9

grouping, 169

$in, 110

null variables, 39

JavaScript, 53-56

$inc, 147

number

key values, grouping, 284

$last, 173

of replica sets, 462

literals, 39

$limit, 172, 287

of servers, 462

MongoClient, 186

$lt, 110

Node.js applications, used

as documents/parameters,
374

$lte, 110

numbers, 38

patterns, prototyping, 55

planning, 11

objects, 9. See also documents

arrays, manipulating, 61
BasicDBObject, 191-194
Collection, 89
Connection, overview of, 86

strings, escape codes, 56

syntax, 53-54
objsLeftInBatch() method, 108
ok property, 145
open() method, 368
operations, atomic write, 15
operator parameter, 287

$match, 172
$max, 173
$min, 173
$mod, 110, 175
$multiply, 175
$ne, 110
$nin, 110
$nor, 110
$not, 110
$or, 110
$pop, 148
$project, 172
$pull, 148

How can we make this index more useful? Email us at [email protected]

517

518

operators

$pullAll, 148

is greater than (>), 42

$push, 148, 173

command-line, 22, 23

$regex, 110

is greater than or equal to

(>=), 42

$rename, 147

is less than (<), 42

$set, 148

documents, PHP Arrays

objects as, 257

$setOnInsert, 147

is less than or equal to (<=),

42

$size, 110

is not equal (!=), 42

group() method, 168

$skip, 172

JavaScript, 40-44

$slice, 148

modulous (%), 40

Node.js applications, objects

used as, 374

$sort, 148, 172

multiplication (*), 40

operator, 287

$strcasecmp, 175

not (!), 42

projection, 133

$substr, 175

or (||), 42

query, 109, 139, 161

$subtract, 175

query, 109-110

parentheses (()), 50

$sum, 173

subtraction (-), 40

partitions, selecting methods,

471-472

update, 146-147

$toLower, 175

parameters

commands, 30-31

fields, 213

$toUpper, 175

optimizing databases, 443-453

passing variables to functions, 50

$type, 110

options, --eval command-line,

31-32

patterns, prototyping objects, 55

$unset, 148
$unwind, 172
addition (+), 40
aggregation
expression, 173-175

or (||) operator, 42
out option, 179

models, planning, 11-17

outputting data in shells, 40

replication, 460. See also

replication

framework, 174-172

PHP applications, 251

and (&&), 42
arithmetic, 40-41

Array objects, 257

data access, 273

assignment, 41
both value and type are equal
(===), 42
both value and type are not
equal (!==), 42
comparison, 42

performance, 17
databases, managing,
443-453

orders, sorting, 128-130

applying aggregation,
287-290

paging
documents, Node.js
applications, 397

grouping results, 283-287

requests, 128

limiting result sets,

273-281

results, 136

searching distinct field

values, 281-283

decrement (--), 40

Java applications, 215

division (/), 40

PHP applications, 278

DB object, 253

fields:value, 110

Python applications, 336

DBCollection object, 279

increment (++), 40

Dictionary objects, 317

is equal to (==), 42

documents, 293

repairDatabase() method

adding, 293-297

Python applications, 311

counting, 265-267

Collection object, 313

deleting, 297-299

Cursor objects, 315, 332

reviewing, 260-262

data access, 331

saving, 299-302

query options, 179

query parameters, 139, 161

searching, 259-265

applying aggregation,
344-347

sorting results, 267-270

grouping results, 341

updating, 302-305

limiting result sets,

331-338

RAM (random access memory),

10

upserting, 305-308

random access memory. See RAM

driver objects, 251-259

Database object, 313

fields, limiting, 276

distinct field values, 339-341

RDBMSs (relational database

management systems), 6-8

GridFS Stores, implementing,

489-493

documents, 349

read role, 71

adding, 349-353

MongoClient object, 252

counting, 324-326

read_preference() method,
312-314

MongoCollection object,
253-254

deleting, 353-355

readAnyDatabase role, 71

saving, 355-357

readPref() method, 108

MongoCursor object, 256,

274-276

searching, 318-324

readWrite role, 71

sorting results, 326-328

readWriteAnyDatabase role, 71

MongoDB object, 253

updating, 358-361

records, converting, 9

results, paging, 278

upserting, 361-364

reduce parameter, 168

write concerns, configuring,

257

fields, limiting, 334

GridFS Stores

pipelines, applying aggregation,

176
planning models, 11-17

references, normalizing data,

12-13

accessing, 496-497

reIndex() method, 89

implementing, 494-497

reindexing collections, 441-443

MongoClient object, 312

port setting, 24

results, paging, 336

519

relational database management

systems. See RDBMSs

primary servers, 460

reliability, 7

print() function, 32

remove() method, 89, 161, 188,

236, 254, 297, 314, 371

print() method, 40
printjson() method, 40

remove_user() method, 313

queries

removeUser() method, 87, 187,

370

privileges, clusterAdmin role, 91

profiling databases, 446-448
projection parameter, 133
prototyping object patterns, 55
push() method, 60

evaluating, 449-451

removing. See deleting

routers, 469

rename() method, 314, 371

starting, 473

renameCollection() method, 89

query operators, 109-110

renaming collections, 435-436

repairDatabase() method, 87

How can we make this index more useful? Email us at [email protected]

520

repairing databases

repairing databases, 453-454

paging, 136

replacing words in strings, 58

PHP applications

replica sets. See also replication

deploying, 462-463
formatting, 463-467
types of, 460
replication, 16, 459
applying, 459-467
strategies, applying, 461
requests

assigning, 71

grouping, 283-287
paging, 278

clusterAdmin privileges, 91
routers

sorting, 267-270

queries, 469

Python application
limiting, 331-338

starting, 473
runCommand() method, 87, 144

sorting, 326-328
Python applications
grouping, 341

manipulating, applying
aggregation, 171-178

sets, limiting, 130-138

Node.js applications, 374

sorting, 128-130

paging, 128

roles

paging, 336

retrieving

PHP applications, applying

aggregation, 287-290

distinct field values, 139,

219, 282, 400

status of database write,

retrieving, 145

documents

S
save() method, 89, 155, 188,
239, 254, 299, 314, 371
saving
databases, 454-455
documents
collections, 155-158, 239

from collections, 112-116

Java applications, 239-241

REST interfaces, 26

Node.js applications,
377-383

Node.js applications,
419-423

rest setting, 24

Python applications, 319

PHP applications, 299-302

results, 30-31

using Java, 195

Python application,
355-357

resetDoc() method, 242

grouping, 167-171, 221-225

Java applications
paging, 215
sorting, 203-206
limiting
Java applications, 209-218
PHP applications, 273-281
manipulating, 181

files, GridFS Stores, 483,

486, 491, 495, 499
specific documents (using
PHP), 262-265
status of database write
requests, 145
return keyword, 50
returning

mapReduce() method,
applying, 178-183

fields, limiting, 212

Node.js applications

values from functions, 50

grouping, 402-406
limiting, 391-399
sorting, 385-388

objects, 132

reviewing documents, PHP

applications, 260-262

scalability, 6
scope
options, 179
variables, 52-53
scripting shells, 31-34
clients, 33-34
executing, 32
searching
array items, 63
contents, 118

slaveOk parameter

distinct field values, 138-140,

218-221

setReadPrefMode() method, 86

counting, 125-127

sets, results. See also results

deleting, 161-163

Node.js applications,
400-402

Java applications, 203-206

PHP applications, 281-283

limiting access in Java

applications, 209-218

saving, 155-158

PHP applications, 273-281

sorting results, 128-130

documents
in shells, 112-116

limiting result sets,

130-138

limiting, 130-138

searching in, 112-116

Java applications, 194-201

setSlaveOk() method, 86

updating, 151-155

Node.js applications,
377-383

setup. See configuring

upserting, 158-160

PHP applications, 259-265

Python application,
318-324
multiple documents, 115

setWriteConcern() method,
186-188

expressions, evaluating,
31-32

shard servers, 469

GridFS Stores, implementing,

482-484

sharding, 16, 459

clusters

JavaScript, 30, 40

results, grouping, 167-171

adding, 473

native methods, 29

specific documents, Node.js

applications, 380

deploying, 472

objects, grouping, 222

formatting, 475-479

results

specific sets of documents,

117-122
substrings in strings, 58
secondary servers, 460
selectCollection() method,
252-253
selectDB() method, 252

collections, enabling, 474

grouping, 167-171

databases, enabling, 474

mapReduce() method,
178-183

implementing, 468-479
keys, selecting, 470-471

scripting, 31-34

servers, types of, 469

starting, 28

tag ranges, configuring, 475

NoSQL, 7-8
partitioning methods, 471-472
RDBMS, 7-8
sharding keys, 470-471
servers

aggregation, applying,
171-178

showWord() method, 300

clients

single field indexes, 439

accessing MongoDB from,

27-31
scripting, 33-34

replication, 460. See also

replication
sharding, types of, 469
serverStatus() method, 87
setReadPreference() method,
186-188, 252,-254, 313

user accounts, formatting, 72

show <option> command, 28

shells

selecting

521

shutdownServer() method, 87

size() method, 108, 191

sizing
collection design, 16

commands, 28, 32-33

documents, 10

constructors, 29

Node.js application results,

limiting, 392-394

databases, managing, 433

documents
adding to collections,
149-151

results, limiting by, 210

skip() method, 108, 136, 191,
216, 256, 316, 373
slaveOk parameter, 434

How can we make this index more useful? Email us at [email protected]

522

snapshot() method

snapshot() method, 108

storage, GridFS Stores, 483

totalIndexSize() method, 89

sorting results, 128-130

storageSize() method, 89

totalSize() method, 89

Java applications, 203-206

strategies, 7

troubleshooting

Node.js applications, 385-388

PHP applications, 267-270

strategies, applying replication,

461

Python application, 326-328

strings

databases
managing, 443-453
repairing, 453-454

arrays

sort option, 179

top command, 451-453

converting, 62

try/catch blocks, 65

splitting, 58

TTL (Time To Live), 17

sort() method, 108, 128, 191,

204, 256, 267, 316, 326, 373,
386

combining, 58

TTL property, 440

sparse property, 440

manipulating, 56-60

types

specific documents

objects, escape codes, 56

data

Node.js applications, 380

substrings, searching, 58

JavaScript, 38-39

PHP, 262-265

words, replacing, 58

MongoDB, 10-11

Python applications, 321

subdocuments, 9, 118. See also

documents

specific sets of documents,

searching, 117-122

subobjects, 13. See also objects

specifying JavaScript files, 32-33

substrings, searching strings, 58

speed, 7

subtraction (-) operator, 40

split() method, 58
splitting strings into arrays, 58

switch statements,
implementing, 44

starting

syntax, objects, 53-54

of indexes, 438-440
of loops, 44-49
of replica sets, 460
of sharding servers, 469

authentication, 79
unique property, 440

MongoDB, 22
query routers, 473
shells, 28
statements

update operators, databases,

146-147
update() method, 89, 188, 242,
254, 302, 305, 314, 371

if, applying, 43-44

tag ranges, configuring

sharding, 475

return, 50

testing databases, 31

switch, implementing, 44

text indexes, 439

collections, 151-155, 243

statistics, viewing, 94-96,

443-444

throwing errors, 66

Java applications, 241-245

stats() method, 89, 95

toArray() method, 108, 191, 373

status of database write requests,

retrieving, 145

todb parameter, 434

stopping MongoDB, 25

Time To Live. See TTL

top command, 451-453

updateExisting property, 145

updating documents, 15

Node.js applications, 423-427

PHP applications, 302-305
Python applications, 358-361
upserted property, 145

wtimeout property

upserting documents

fields

collections, 158-160, 246

searching based on, 117

Java applications, 245-249

searching distinct,
138-140, 218-221

Node.js applications, 427-431

PHP applications, 305-308

functions, returning, 50

Python application, 361-364

key, grouping objects, 169

usability, 10

null variables, 39

use <database> command, 28

subdocuments, searching,
118

use <new_database_name>
command, 92

var keyword, 38

user accounts

variables

authentication, starting, 79

defining, 37-38

formatting, 72

functions, passing, 50

managing, 70-78

scope, 52-53

user administrator accounts,

formatting, 78

verbose option, 179

userAdminAnyDatabase role, 71

version() method, 87

userAdmin role, 71

viewing
collections, 96

users

databases

deleting, 77

lists, 91

documents, counting, 126

stats, 94-96

lists, 74

write requests, retrieving status of

database, 145
write_concern() method, 312-314
wtime property, 145
wtimeout property, 145

verbose setting, 24

username parameter, 434

statistics, 443-444

validate() method, 92

waited property, 145

validating databases, 444-446

while loops, 45

values

wnote property, 145

arrays, searching documents

based on, 117

words, replacing strings, 58

documents, searching, 118

configuring, 143-144

523

write concerns

Node.js applications, 374

PHP applications, 257
Python applications, 317

How can we make this index more useful? Email us at [email protected]