MongoDB classes 2019

Mongo DB
06/06/2019 MongoDB class by Alexandre Bergere 1

{
Part One:[
Big Data
No SQL
],
Part Two:[
Mongo DB
Architecture & Modelization
CRUD
Replication
Security
Aggregation
Mongo DB Atlas
]
}

MongoDB class by Alexandre Bergere 3
alexandre.bergere@gmail.com
https://fr.linkedin.com/in/alexandrebergere
@AlexPhile
Avanade
2016 - 2019
Sr Anls, Data Engineering
Worked for 3 years as a senior analyst at
Avanade France, I have developed my skills
in data analysis (MSBI, Power BI, R, Python,
Spark, Cosmos DB) by working on innovative
projects and proofs of concept in the energy
industry.
ESAIP
Teacher
2016 - x
Data Freelance
2019 - x

Sources
A lot of the sources for making this courses provided from docs.mongodb.com or
https://www.university.mongodb.com.

BIG DATA

Data Source
Big Data Architecture
Data Ingestion & Processing Data Analytics Data Visualization
Data Storage
Data Lake / Data Warehouse
ETL
Messaging Queue
Data Management
Batch / Streaming
Machine Learning MOLAP Data Quality
No SQL
HDFS
SQL
Web Apps
Visualizations tools
Visuals Query
RDBMS
Social Media
Device
IoT / Sensors
Files (log, Unst)
Object store

Data Storage
Relational data store HDFS Key Value data store Columnar data store
Object store Search data store Graph data store Document data store

NO SQL

Data management
NoSQL
OLAP
System R & SQL
Cobol
Hierarchic model
70’s
80’s
90’s
20th

NoSQL
OLAP
System R & SQL
Cobol
Hierarchic model
Codd's 12 Rules
o Rule 1: Information Rule
o Rule 2: Guaranteed Access Rule
o Rule 3: Systematic Treatment of NULL Values
o Rule 4: Active Online Catalog
o Rule 5: Comprehensive Data Sub-Language Rule
o Rule 6: View Updating Rule
o Rule 7: High-Level Insert, Update, and Delete Rule
o Rule 8: Physical Data Independence
o Rule 9: Logical Data Independence
o Rule 10: Integrity Independence
o Rule 11: Distribution Independence
o Rule 12: Non-Subversion Rule
Data management
RDBMS

NoSQL
OLAP
System R & SQL
Cobol
Hierarchic model
Data management
OLAP : Online Analytical Processing

Data management
No SQL
NoSQL
OLAP
System R & SQL
Cobol
Hierarchic model
Benefits:
o performance
o volume
o variety
Different type of data storage:
o Key-value
o Document data store
o Columnar data store
o Graph data store
o Search data store

MongoDB

Created in 2007 & first release
in 2010.
Easy and simple … as a leaf.
Document data store &
Schemaless.

Nexus Architecture

Drivers & Frameworks

Mongo DB is easy
For many developers, data model goes hand in hand with object mapping, and for that purpose
you may have used an object-relational mapping library, such as Java’s Hibernate framework or
Ruby’s ActiveRecord.
Such libraries can be useful for efficiently building applications with a RDBMS, but they’re less
necessary with MongoDB. This is due in part to the fact that a document is already an object-
like representation. It’s also partly due to the MongoDB drivers, which already provide a fairly
high-level interface to MongoDB. Without question, you can build applications on MongoDB
using the driver interface alone.

Use cases
o Web application (mongoDB is well-suited as primary datastore for web application)
o Agile development
o Analytics and logging
o Caching
o Variable Schemas

The case for adding NoSQL
o Large volumes of rapidly changing structured, semi-structured, and unstructured data
o Agile sprints, quick schema iteration, and frequent code pushes
o API-driven, object-oriented programming that is easy to use and flexible
o Geographically distributed scale-out architecture instead of expensive, monolithic
architecture
Consider, for example, enterprise resource planning (ERP), a standard for relational databases.
What if you want to offer ERP forms users can actually modify if they need to? A document-
based NoSQL database such as MongoDB can provide that functionality without requiring you
to rebuild your whole data schema every time a user wants to change the data format.

Mongo DB history

Mongo DB 4.0 : ACID transactions
More info.

Leader in The Forrester Wave™: Big Data NoSQL, Q1 2019
o “MongoDB remains the most popular
NoSQL database”
o Used by more than 8,000 companies,
including many Fortune 100
companies.
o Highest possible scores in 21 of the
26 criteria.

Companies

White papers
MongoDB – BI &
Analytics
MongoDB – Kafka MongoDB – Spark

Modelization

Document are rich data structure
• JSON:
• String, Number, Array, Object, NULL, Boolean.
• BSON:
• Date, BinData, ObjectID, Geo-Location.
• Better storage performance.
ObjectID:
◦ _id : 'DATE[4] | MAC_ADDR[3] | PID[2] | COUNTER[3]

Available Types
Type Number Alias Notes
Double 1 “double”
String 2 “string”
Object 3 “object”
Array 4 “array”
Binary data 5 “binData”
Undefined 6 “undefined” Deprecated.
ObjectId 7 “objectId”
Boolean 8 “bool”
Date 9 “date”
Null 10 “null”
RegularExpression 11 “regex”
DBPointer 12 “dbPointer” Deprecated.
JavaScript 13 “javascript”
Symbol 14 “symbol” Deprecated.
JavaScript (with scope) 15 “javascriptWithScope”
32-bit integer 16 “int”
Timestamp 17 “timestamp”
64-bit integer 18 “long”
Decimal128 19 “decimal” New in version 3.4.
Min key -1 “minKey”
Max key 127 “maxKey”

Documents are Flexible

Document Model
Pers_ID Surname First_Name City
0 Miller Paul London
1 Ortega Alvaro Valencia
2 Huber Urs Zurich
3 Blanc Gaston Paris
4 Bertolini Fabrizio Rome
Car_ID Model Year Value Pers_ID
101 Bently 1973 100000 0
102 Rolls Royce 1965 330000 0
103 Peugot 1993 500 3
104 Ferrari 2005 150000 4
105 Renault 1998 2000 3
106 Renault 2001 7000 3
107 Smart 1999 2000 2
CAR
PERSON
Mongo DB
RDBMS

TP - Modelization
1. Transform this address « 125 avenue de la république, 75011, PARIS » in BSON object.
2. Transform this 2 addresses « 125 avenue de la république, 75011, PARIS » and « 34 rue Ferdinand,
75012, PARIS » in an array.
3. Transform the schema below on BSON document.
ID LastName FirstName Age
1 BERGERE Alexandre 26
Address ID People
125 avenue de la république, 75011,
PARIS
1
34 rue Ferdinand,
75012, PARIS
1
1 n

MongoDB - Starter

SQL vs MongoDB Terms
SQL Terms/Concepts MongoDB Terms/Concepts
Database Database
Table Collection
Line Document
Column Field
Index Index
Join Embeded or linked document
Primary key Primary key (start by « _id »)

Storage
o MMAPv1
o WiredTiger
o In Memory

Installation

Launch instance
Launch as a service:
o mongod --dbpath C:UsersalexaDocumentsMongoDBdata -- logpath
C:UsersalexaDocumentMongoDBlogs.log
Launch the conection:
o mongo
Launch a shard:
o mongos
Original Shortcut
--db -d
--collection -c
--username -u
--password -p
--host -h
Options:

The Javascript console
var authColl = db.getCollection("auth")
authColl.insertOne(
{
usrName : "John Doe",
usrDept : "Sales",
usrTitle : "Executive Account Manager",
authLevel : 4,
authDept : [ "Sales", "Customers"]
}
)

DML

DML
# Returns all database
> show dbs
# The current database name:
> db.getName()
# Returns all database
> show dbs
# Returns all collection in the current database:
> db.getCollectionNames()
# Returns a collection or a view object:
> db.getCollection(name)
# The current database connection:
> db.getMongo()
# Clean the console log:
> cls
# Return collection informations:
> db.getCollectionInfos({name: "name"})

DML
# Removes the current database:
> db.dropDatabase()
# Copies a database to another database on the current host:
>db.copyDatabase(fromdb, todb, fromhost, usern
ame, password, mechanism)
# Copies a database from a remote host to the current host:
> db.cloneDatabase("hostname")
# Rename collection:
> db.renameCollection({ renameCollection:
"fromCollection", to: " toCollection" })
> use test
Or
> db.orders.renameCollection( "toCollection" )
# Copies data directly between MongoDB instances:
> db.cloneCollection(from, collection, query)

Stats
# Returns statistics that reflect the use state of a single database or
collection.
> db.stats()
> db.collection.stats()
{
"ns" : "guidebook.restaurants",
"count" : 25359,
"size" : 10630398,
"avgObjSize" : 419,
"storageSize" : 4104192
"capped" : false,
"wiredTiger" : {
"metadata" : {
"formatVersion" : 1
}, […]
"nindexes" : 4,
"totalIndexSize" : 626688,
"indexSizes" : {
"_id_" : 217088,
"borough_1_cuisine_1" : 139264,
"cuisine_1" : 131072,
"borough_1_address.zipcode_1" :
139264
}

Command-line tools
Launch in the shell, not in mongoDB instance.

Import or export document
mongoexport and mongoimport: Export and import JSON, CSV, and TSV7 data.
# Import multiples document:
mongoimport -d crunchbase -c companies
C:UsersalexaDocumentsMongoDBsrccompanies.json
# Import multiples document in an array:
mongoimport -d crunchbase -c artists --file
C:UsersalexaDocumentsMongoDBsrcartists.json --jsonArray
# Export collection:
mongoexport --db crunchbase --collection artists --out artists.json

Backup
mongodump
mongodump
--host
--port
--db
--username
--password (when specifying the password as part of the URI connection string)
--authenticationDatabase
--authenticationMechanism
# mongodump a Collection:
mongodump --db test --collection collection
# mongodump a Database:
mongodump –archive=test.20100224.archive –db Crunchbase

Restore
mongostore
mongostore
--host
--port
--collection /pwd –db /pwd
--db /pwd
--username
--password
--authenticationDatabase
<path to the backup>
# Output an Archive to Standard Output:
mongodump --archive --db test --port 27017 | mongorestore --archive --port 27018

Others
mongostore
o mongosniff: A wire-sniffing tool for viewing operations sent to the database. It essentially
translates the BSON going over the wire to human-readable shell statements.
o mongostat: Similar to iostat, this utility constantly polls MongoDB and the system to provide
helpful stats, including the number of operations per second (inserts, queries, updates, deletes,
and so on), the amount of virtual memory allocated, and the number of connections to the
server.
o mongotop: Similar to top, this utility polls MongoDB and shows the amount of time it spends
reading and writing data in each collection.
o mongoperf: Helps you understand the disk operations happening in a running MongoDB
instance.
o mongooplog: Shows what’s happening in the MongoDB oplog.
o Bsondump: Converts BSON files into human-readable formats including JSON.

CRUD

> create
# Create a database
> {
create: <collection or view name>,
capped: <true|false>,
autoIndexId: <true|false>,
size: <max_size>,
max: <max_documents>,
flags: <0|1|2|3>,
storageEngine: <document>,
validator: <document>,
validationLevel: <string>,
validationAction: <string>,
indexOptionDefaults: <document>,
viewOn: <source>,
pipeline: <pipeline>,
collation: <document>
}

Capped collection
Distinguished from standard collectionsby their fixed size. This means that once a capped
collection reaches its maximum size, subsequent inserts will overwrite the least-recently-
inserted documents in the collection.
This design prevents users from having to prune the collection manually when only recent data
may be of value.
> {
create: <collection or view name>,
capped: <true|false>
[…]
}
Designed for high-performance logging scenarios.

> find
# FIND()
> db.<collection>.find ({<conditions>},{<champs>})
> db.products.find( { qty: { $gt: 25 } }, { item: 1, qty: 1 } )
sort, first, skip, second, and limit last because that is the
only order that makes sense.
# Options:
>
.pretty()
.sort() : 1 : ASC, -1: DESC :
sort({‘name’:-1})
.skip() : number
.limit() : number
.count()

Partial Match Queries in Users
# Use regular expression:
> db.users.find({'last_name': /^Ber/})

> insert
# INSERT()
> db.<collection>.insert ({<value>})
> db.<collection>.insertMany([{<values>}])
> db.inventory.insertMany([
{ item: "journal", qty: 25, tags: ["blank", "red"], size: { h: 14, w: 21, uom:
"cm" } },
{ item: "mat", qty: 85, tags: ["gray"], size: { h: 27.9, w: 35.5, uom: "cm" } },
{ item: "mousepad", qty: 25, tags: ["gel", "blue"], size: { h: 19, w: 22.85,
uom: "cm" } }
])
db.collection.insertOne() Inserts a single document into a collection.
db.collection.insertMany() db.collection.insertMany() inserts multiple documents into a collection.
db.collection.insert()
db.collection.insert() inserts a single document or multiple documents into
a collection.

> update
# UPDATE()
> db.<collection>.update
({<conditions>},{<champs>},{upsert:true/false},{multi:true/false}
)
> { "_id": "artist:281", "last_name": "Cotillard", "first_name": "Marion", "birth_date": "1975" }
# Operator Update:
> db.artists.update({"_id": "artist:281"},{ $set : {"last_name" : "Page"}})
> { "_id": "artist:281", "last_name": “Page", "first_name": "Marion", "birth_date": "1975" }
# Replacement Update:
> db.artists.update({"_id": "artist:281"},{"last_name" : "Page"})
> { "_id": "artist:281", "last_name": “Page"} ❑ Operator Update
❑ Replacement Update
All updates require at least two arguments. The first specifies which documents to update, and
the second defines how the selected documents should be modified

> update
Upsert: boolean Optional. If set to true, creates a new document when no document
matches the query criteria. The default value is false, which does not insert a new document
when no match is found.
Multi: boolean Optional. If set to true, updates multiple documents that meet the query
criteria. If set to false, updates one document. The default value is false.
# UPDATE()
> db.<collection>.update ({<conditions>},{<champs>}
,{upsert:true/false}
,{multi:true/false}
)
> db.pageview.update({'_id':'/potager/users'},{$inc:{'views':1}},{upsert:true})

Query Operator
Name Description
$eq Matches values that are equal to a specified value.
$gt Matches values that are greater than a specified value.
$gte Matches values that are greater than or equal to a specified value.
$lt Matches values that are less than a specified value.
$lte Matches values that are less than or equal to a specified value.
$ne Matches all values that are not equal to a specified value.
$in Matches any of the values specified in an array.

Query Operator
Name Description
$set Sets the value of a field in a document.
$unset Removes the specified field from a document.
$inc Increments a field by a specified value.
$rename updates the name of a field
$muc Multiply the value of a field by a number
> db.products.update( { _id: "56c0befa5e435acc1d4a5fbd"}, { $inc: { quantity: -2}
})

Query Operator : $set
# $set
> db.products.update(
{ _id: 100 },
{ $set:
{
quantity: 500,
details: { model: "14Q3", make: "xyz" },
tags: [ "coats", "outerwear", "clothing" ]
}
}
)
# $set Embedded Documents
{ _id: 100 },
{ $set: { "details.make": "zzz" } }
)
# $set in Arrays
{ _id: 100 },
{ $set:
{
"tags.1": "rain gear",
"ratings.0.rating": 2
}
}
)

Array
{
_id: 1,
fruits: [ "apples", "pears", "oranges", "grapes", "bananas" ],
vegetables: [ "carrots", "celery", "squash", "carrots" ]
}
{
_id: 2,
fruits: [ "plums", "kiwis", "oranges", "bananas", "apples" ],
vegetables: [ "broccoli", "zucchini", "carrots", "onions" ]
}
> db.stores.update(
{ },
{ $pull: { fruits: { $in: [ "apples", "oranges" ] }, vegetables: "carrots" } },
{ multi: true }
)

Query Operator : Arrays
Name Description
$set Sets the value of a field in a document.
$unset Removes the specified field from a document.
$inc Increments a field by a specified value.
$rename updates the name of a field
$muc Multiply the value of a field by a number
> db.products.update( { _id: "56c0befa5e435acc1d4a5fbd"}, { $inc: { quantity: -2}
})

> delete
# DELETE()
> db.<collection>.remove ({<conditions>})
> db.artists.remove({"_id": "artist:39"})
# Remove all fields
> db.artists.remove({})

TP - Modelization
1. Import the json document “veg_garden” into
mongoDB.
2. Return all vegetable garden with an existing
property of “number”.
3. Return all vegetable garden with an existing
property of “harvest”.
4. Return all vegetable garden with a service’ title
“Classes”.
5. Return all vegetable garden with a sale’s address
number 52.
6. Return all vegetable garden that have the product
97.
7. Import json documents “companies” and “artists”
into mongoDB.
8. Return the number of companies with a number
of employees less or equal to 45.
9. Return artists from the 6th to the 9th ordered desc
by their name.
10. Insert the following artist:
"_id": "artist:9", "last_name": "Bergere",
"first_name": "Alexandre", "birth_date": "1992“.
11. Add « golf » on artist’s hobbies with the id 280.
12. Add « yoga » on artist’s hobbies with the id 282.
13. Delete hobbies « pony » and « painting » from the
artist 280.

TP - Modelization
# 1. Import the json document “veg_garden” into mongoDB.
mongoimport -d crunchbase -c vegGarden --file C:UsersalexCoursMongoDB2018-2019srcveg_garden.json --
jsonArray
# 2. Return all vegetable garden with an existing property of “number”.
> db.vegGarden.find({"number":{$exists:true}}).pretty()
# 3. Return all vegetable garden with an existing property of “harvest”.
> db.vegGarden.find({"harvest":{$exists:true}}).pretty()
# 4. Return all vegetable garden with a service’s title “Classes”.
> db.vegGarden.find({"service.title":“Classes"}).pretty()
# 5. Return all vegetable garden with a sale’s address number 52.
> db.vegGarden.find({"adresse.sale.num":52}).pretty()
# 6. Delete hobbies « pony » and « painting » from the artist 280.
> db.vegGarden.find({"products":{$in:[97]}})

TP - Modelization
# 7. Import json documents “companies” and “artists” into mongoDB.
mongoimport -d crunchbase -c artists --file C:UsersalexCoursMongoDB2018-2019srcartists.json --
jsonArray
mongoimport -d crunchbase -c companies C:UsersalexCoursMongoDB2018-2019srccompanies.json
# 8. Return the number of companies with a number of employees less or equal to 45.
> db.companies.count({number_of_employees:{$lte:45}})
# 9. Return artists from the 6th to the 9th ordered desc by their name
> db.artists.find().pretty().sort({"last_name":-1}).skip(5).limit(4)
# 10. Insert the following artist:
"_id": "artist:9", "last_name": "Bergere", "first_name": "Alexandre", "birth_date": "1992" .
Remplacer le numéro d’id par 282.
> db.artists.insert({ "_id": "artist:9", "last_name": "Bergere", "first_name": "Alexandre", "birth_date":
"1992" })
# 11. Add « golf » on artist’s hobbies with the id 280.
> db.artists.update({"_id": "artist:280"},{$push:{"hobbies":"golf"}})
# 12. Add « yoga » on artist’s hobbies with the id 282.
> db.artists.update({"_id": "artist:282"},{$push:{"hobbies":"yoga"}})
# 13. Retirer les hobbies « poney » et « photo » à l’artiste 280.
> db.artists.update({"_id": "artist:280"},{$pull:{"hobbies": {$in:["pony","photo"]}}})

Schema Validation

Schema validation
• Implement data governance without sacrificing
the agility that comes from a dynamic schema.
• With schema validation, developers and
operations spend less time defining data
quality controls in their applications, and
instead delegate these tasks to the database.
To specify validation rules when creating a new collection, use with the valid
db.createCollection() option.
To add document validation to an existing collection, use collMod command with the validator
option.

Example of schema validation
# Create a database
> db.createCollection("students", {
validator: {
$jsonSchema: {
bsonType: "object",
required: [ "name", "year", "major", "gpa" ],
additionalProperties: true,
properties: {
name: {
bsonType: "string",
description: "must be a string and is required"
},
gender: {
bsonType: "string",
description: "must be a string and is not required"
},
year: {
bsonType: "int",
minimum: 2017,
maximum: 3017,
exclusiveMaximum: false,
description: "must be an integer in [ 2017, 3017 ]
and is required"
}
> […] major: {
enum: [ "Math", "English",
"Computer Science", "History", null ],
description: "can only be
one of the enum values and is required"
},
gpa: {
bsonType: [ "double" ],
minimum: 0,
description: "must be a
double and is required"
}
}
}
}
})

Query expression
In addition to JSON Schema validation, MongoDB supports validation with query filter
expressions using the query operators, with the exception of $near, $nearSphere, $text, and
$where.
> db.createCollection( "contacts",
{ validator: { $or:
[
{ phone: { $type: "string" } },
{ email: { $regex: /@mongodb.com$/ } },
{ status: { $in: [ "Unknown", "Incomplete" ] } }
]
}
} )

Add a validator to an existing collection
In addition to JSON Schema validation, MongoDB supports validation with query filter
expressions using the query operators, with the exception of $near, $nearSphere, $text, and
$where.
> db.runCommand( {
collMod: "contacts",
validator: { $jsonSchema: {
bsonType: "object",
required: [ "phone", "name" ],
properties: {
phone: {
bsonType: "string",
},
name: {
bsonType: "string",
}
}
} },
validationLevel: "moderate"
} )
collMod

Validation level & action
ValidationLevel Description
"off" disable validation entirely.
"strict"
If the validationLevel is strict (the default), MongoDB
applies validation rules to all inserts and updates.
"moderate"
If the validationLevel is moderate, MongoDB applies
validation rules to inserts and to updates to existing
documents that already fulfil the validation criteria. With
the moderate level, updates to existing documents that do
not fulfill the validation criteria are not checked for
validity.
validationAction Description
"error"
Default Documents must pass validation before the write
occurs. Otherwise, the write operation fails.
"warn"
Documents do not have to pass validation. If the document
fails validation, the write operation logs the validation
failure.
ValidationLevel option, which determines how strictly MongoDB
applies validation rules to existing documents during an update.
ValidationAction option, which determines whether MongoDB
should error and reject documents that violate the validation rules or
warn about the violations in the log but allow invalid documents.

Bypass Document Validation
Users can bypass document validation on commands and methods that support the
bypassDocumentValidation option. The following commands and their equivalent methods
support bypassing document validation:
oaggregate
oapplyOps
ocloneCollection on the destination collection
oclone on the destination
ocopydb on the destination
ofindAndModify
oinsert
omapReduce
oUpdate
For deployments that have enabled access control, to bypass document validation, the
authenticated user must have bypassDocumentValidation action. The built-in roles dbAdmin
and restore provide this action.

TP – Schema Validation
1. Add the following schema validation to the artists’ collection:
• "last_name","first_name","status" required.
• “status” can take only this two values: "alive“ or "dead"
2. Try to insert the following artist: { "last_name": "Katerine", "first_name": "Philippe"}
3. Update the artist with the id “artists:281”, by modify his name by “Kheirona”.
4. Change validation level in « moderate ».
5. Try again the update in question 3.
6. Change validation action in « warn », then insert again the artist in question 2.

# 1. Add the following schema validation to the artists’ collection:
> db.runCommand({
collMod: "artists",
validator:{ $jsonSchema:{
bsonType: "object",
required:["last_name","first_name","status"],
properties:{
last_name:{
bsonType: "string",
description:"must be a string and is required"
}
,first_name:{
bsonType: "string",
description:"must be a string and is required"
}
,status:{
enum: ["alive", "dead"],
description:"must be a alive or dead and is required"
}
}
},
}
,validationLevel: "strict"
})

# 1. Option 2:
> db.runCommand({
collMod: "artists",
validator:{
$and:
[
{ last_name: { $type: "string" } },
{ first_name: { $type: "string" } },
{ status: { $in: [ "alive", "dead" ] } }
],
$jsonSchema:{
required:["last_name","first_name","status"]
},
}
,validationLevel: "strict"
})

# 2. Try to insert the following artist: { "last_name": "Katerine", "first_name":
"Philippe"}
> db.artists.insert({ "last_name": "Katerine", "first_name": "Philippe"}) –
{failed}
# 3. Update the artist with the id “artists:281”, by modify his name by
“Kheirona”.
> db.artists.update({"_id": "artist:281"},{ $set:{ "last_name": " Kheirona" }})
# 4. Change validation level in « moderate ».
> db.runCommand({
collMod: "artists"
,validationLevel : "moderate"
})
# 6. Change validation action in « warn », then insert again the artist in question
2.
db.runCommand({
collMod: "artists"
,validationAction: "warn"
})
2018-12-01T12:31:23.738-0500 W STORAGE [conn1] Document would fail validation collection: example.contacts2 doc: { _id:
ObjectId('5a2191ebacbbfc2bdc4dcffc’), last_name: " Kheirona "}

One to many

One to N
One to few

One to N
One to many

One to N
{
_id: ObjectId("6a5b1476238d3b4dd5000048"),
slug: "gardening-tools",
name: "Gardening Tools",
description: "Gardening gadgets galore!",
parent_id: ObjectId("55804822812cb336b78728f9"),
ancestors: [
{
name: "Home",
_id: ObjectId("558048f0812cb336b78728fa"),
slug: "home"
},
{
name: "Outdoors",
_id: ObjectId("55804822812cb336b78728f9"),
slug: "outdoors"
}
]
}
> db.products.find({category_ids:
ObjectId('6a5b1476238d3b4dd5000048')})

One to N
{
_id: ObjectId("6a5b1476238d3b4dd5000048"),
slug: "gardening-tools",
name: "Gardening Tools",
description: "Gardening gadgets galore!",
parent_id: ObjectId("55804822812cb336b78728f9"),
ancestors: [
{
name: "Home",
_id: ObjectId("558048f0812cb336b78728fa"),
slug: "home"
},
{
name: "Outdoors",
_id: ObjectId("55804822812cb336b78728f9"),
slug: "outdoors"
}
]
}
# $set in Arrays
> db.products.find({category_ids:
ObjectId('6a5b1476238d3b4dd5000048')})
# To query for all categories from a given product:
> var product = db.products.findOne({"slug":
"wheelbarrow-9092"})
> db.categories.find({_id: {$in:
product['category_ids']}})

TP – One to Many
Student Subject

TP – One to Many
# Student:
> db.student.insertMany([
{
"name":"bergere",
"surname":"alex",
"subject":[
{
"id_ subject": "MongoDB"
,"note" : [15,13]
},
{
"id_subject": "NodeJS"
,"note" : [12,13]
}
]
},
{
"name":"Fauchard",
"surname":"Than Tuan",
"subject":[
{
,"note" : [12,18]
},
{
,"note" : [15,8]
}
]
}
])

TP – One to Many
# Subject:
> db.subject.insertMany([
{
"_id":"MongoDB"
,"nom":"MongoDB"
,"salle":"A09"
,"prof":"Alexandre Bergere"
},
{
"_id":"NodeJS"
,"nom":"NodeJS"
,"salle":"A12"
,"prof":"Thierry Dupont"
}
])

TP – One to Many
# Request:
> var subject = []
> db.subject.find().forEach(function(u) { subject.push(u._id) })
> db.student.find({"subject.id_ subject": {$in: subject}})

TP – Many to Many
Student Subject

TP – Many to Many
# Student:
> db.student.insertMany([
{
"_Id" : ObjectID("23109834091209"),
"name":"bergere",
"surname":"alex",
"subject":[
{
,"note" : [15,13]
},
{
,"note" : [12,13]
}
]
},
{
"_Id" : ObjectID("97099230912812"),
"name":"Fauchard",
"surname":"Than Tuan",
"subject":[
{
,"note" : [12,18]
},
{
,"note" : [15,8]
}
]
}

TP – Many to Many
# Subject:
> db.subject.insertMany([
{
"_id":"MongoDB"
,"nom":"MongoDB"
,"salle":"A09"
,"prof":"Alexandre Bergere"
,"Students":[
{
"Prom":"ir2016",
"Student_id":[ObjectID("97099230912812"),
ObjectID("23109834091209")]
}
]
},
{
"_id":"NodeJS"
,"nom":"NodeJS"
,"salle":"A12"
,"prof":"Thierry Dupont"
,"Students":[
{
"Prom":"ir2016",
"Student_id":[ObjectID("97099230912812"),
ObjectID("23109834091209")]
}
]
}
])

$lookup
> {
$lookup:
{
from: <collection to join>,
localField: <field from the input documents>,
foreignField: <field from the documents of the "from" collection>,
as: <output array field>
}
}

$lookup
db.orders.insert([
{ "_id" : 1, "item" : "almonds", "price" : 12, "quantity" : 2 },
{ "_id" : 2, "item" : "pecans", "price" : 20, "quantity" : 1 },
{ "_id" : 3 }
])
db.inventory.insert([
{ "_id" : 1, "sku" : "almonds", description: "product 1", "instock" : 120 },
{ "_id" : 2, "sku" : "bread", description: "product 2", "instock" : 80 },
{ "_id" : 3, "sku" : "cashews", description: "product 3", "instock" : 60 },
{ "_id" : 4, "sku" : "pecans", description: "product 4", "instock" : 70 },
{ "_id" : 5, "sku": null, description: "Incomplete" },
{ "_id" : 6 }
])

$lookup
> db.orders.aggregate([
{
$lookup:
{
from: "inventory",
localField: "item",
foreignField: "sku",
as: "inventory_docs"
}
}
])
{
"_id" : 1,
"item" : "almonds",
"price" : 12,
"quantity" : 2,
"inventory_docs" : [
{ "_id" : 1, "sku" : "almonds", "description" : "product 1", "instock" :
120 }
]
}
{
"_id" : 2,
"item" : "pecans",
"price" : 20,
"quantity" : 1,
{ "_id" : 4, "sku" : "pecans", "description" : "product 4", "instock" :
70 }
]
}
{
"_id" : 3,
{ "_id" : 5, "sku" : null, "description" : "Incomplete" },
{ "_id" : 6 }
]
}06/06/2019 MongoDB class by Alexandre Bergere 88

TP – $lookup
# Subject:
> db.subject.aggregate([
{
$lookup:
{
from: "student",
localField: "_id",
foreignField: "subject.id_
subject",
as: "student"
}
}
])
# Student:
> db.student.aggregate([
{
$lookup:
{
from: "subject",
localField: "subject.id_
subject",
foreignField: "_id",
as: "description"
}
}
])

Index

Index
Indexes are special data structures [1] that store a small portion of the collection’s data set in an easy to
traverse form. The index stores the value of a specific field or set of fields, ordered by the value of the
field. The ordering of the index entries supports efficient equality matches and range-based query
operations. In addition, MongoDB can return sorted results by using the ordering in the index.

Index
# Create
> db.collection.createIndex({'name':1})
# Get
> db.collection.getIndexes()
# Delete
> db.collection.dropIndex({'name':1})

$text

$text
$text performs a text search on the content of the fields indexed with a text index. A $text expression has the
following syntax:
{
$text:
{
$search: <string>,
$language: <string>,
$caseSensitive: <boolean>,
$diacriticSensitive: <boolean>
}
}
> db.articles.find( { $text: { $search:
"coffee" } } )

$text - indexation
Indexes
A collection can have at most
one text index.
> db.collection.createIndex( { comments: "text" } )
# You can index multiple fields for the text index:
> db.collection.createIndex(
{
subject: "text",
comments: "text"
}
)
First, create your index !
Wildcard Text Indexes
When creating a text index on multiple fields, you can also use the wildcard
specifier ($**). With a wildcard text index, MongoDB indexes every field
that contains string data for each document in the collection. The following
example creates a text index using the wildcard specifier:
db.collection.createIndex( { "$**": "text" } )

$text
Case Insensitivity
The version 3 text index supports the common C, simple S, and for Turkish
languages, the special T case foldings as specified in Unicode 8.0 Character
Database Case Folding.
The case foldings expands the case insensitivity of the text index to include
characters with diacritics, such as é and É, and characters from non-Latin
alphabets, such as “И” and “и” in the Cyrillic alphabet.
Version 3 of the text index is also diacritic insensitive. As such, the index
also does not distinguish between é, É, e, and E.
Previous versions of the text index are case insensitive for [A-z] only; i.e.
case insensitive for non-diacritics Latin characters only . For all other
characters, earlier versions of the text index treat them as distinct.

$text - indexation
Case Insensitivity
Match Any of the Search Terms
If the search string is a space-delimited string, $text operator performs a logical OR
search on each term and returns documents that contains any of the terms.
Search for a Phrase
To match the exact phrase as a single term, escape the quotes.
Exclude Documents That Contain a Term
A negated term is a term that is prefixed by a minus sign -. If you negate a term, the
$text operator will exclude the documents that contain those terms from the results.
Search a Different Language
Use the optional $language field in the $text expression to specify a language that
determines the list of stop words and the rules for the stemmer and tokenizer for the
search string.
If you specify a language value of "none", then the text search uses simple
tokenization with no list of stop words and no stemming.
> db.articles.find( { $text: { $search: "bake coffee cake" } } )
> db.articles.find( { $text: { $search: ""coffee shop"" } } )
> db.articles.find( { $text: { $search: "coffee -shop" } } )
> db.articles.find({ $text: { $search: "leche", $language: "es"
} })

TP – $text
1. Find in collection « companies » the following words: “Server” & “Software” in the fields
“description” and “name”.

TP – $text
# Request:
> db.companies.createIndex(
{
name: "text",
description: "text"
}
)
> db.companies.find( { $text: { $search: "Server Software" } } )
> db.companies.find( { $text: { $search: "Server Software" } },
{'description':1,'name':1} ).pretty()

Compass

MongoDB Compass

MongoDB Compass
Visualize, understand, and work with your geospatial data
Point and click to construct sophisticated queries, execute
them with the push of a button and Compass will display your
results both graphically and as sets of JSON documents.
A better approach to CRUD makes it easier to interact with your
data
Modify existing documents with greater confidence using the
intuitive visual editor, or insert new documents and clone or
delete existing ones in just a few clicks.

MongoDB Compass
Compass Community
Editions
View, add, and delete databases and collections X X
View and interact with documents with full CRUD functionality X X
Build and run ad hoc queries X X
View and optimize query performance with visual explain plans X X
Manage indexes: view stats, create, and delete X X
Create and execute aggregation pipelines X X
Kerberos, LDAP and x509 Authentication X
Schema Analysis X
Real Time Server Stats X
Document Validation X

MongoDB Compass
Compass Readonly Edition
New in version 1.12.0
A read-only version of MongoDB Compass is available which provides the ability to limit
certain CRUD operations within your organization. In this version, users are limited strictly
to read operations within MongoDB.
Compass Isolated Edition
New in version 1.14.0
Compass Isolated Edition restricts network requests to TLS-encrypted TCP connections to the
server chosen on the Connect screen. All other outbound connections are not permitted in this
edition.

TP - Compass
1. Insert the following artist: {“last_name”: “Van gogh”, "first_name": “Vincent”}
2. Add hobbies “pony” and “painting” to the artist 280.
3. Add "birth_date" to the schema validation.
4. Return artists from the 6th to the 9th ordered desc by their name.
5. Free test
Artist collection:

Hackolade

Replica set

Replica Set
A replica set in MongoDB is a group of mongod processes that maintain the same data set. Replica sets provide
redundancy and high availability, and are the basis for all production deployments. This section introduces
replication in MongoDB as well as the components and architecture of replica sets. The section also provides
tutorials for common tasks related to replica sets.
Replication provides redundancy and increases data availability. With multiple copies of data on different
database servers, replication provides a level of fault tolerance against the loss of a single database server.
In some cases, replication can provide increased read capacity as clients can send read operations to different
servers. Maintaining copies of data in different data centers can increase data locality and availability for
distributed applications. You can also maintain additional copies for dedicated purposes, such as disaster
recovery, reporting, or backup

Replica set
27017 27018
27019
Primary Arbiter
Secondary
REPLICATION
Types de serveur:
• primary
• secondary
• arbiter
• hidden

Replica set

Replica set
options
mongod --port 27001
--replSet name
--dbpath paht of data
--logpath user
--logappend (if the server shutdown)
--oplogSize 50
mongod --port 27017 --dbpath
"C:UsersalexaDocumentsMongoDBdata_primary" --replSet rs0 --
smallfiles --oplogSize 128
"C:UsersalexaDocumentsMongoDBdata_secondary" --replSet rs0 --
"C:UsersalexaDocumentsMongoDBdata_arbitrer" --replSet rs0 --

Replica set
Replica
Options:
• arbitrerOnly : true (à aucunes données et permet de voter lors d'un
nombre paire de serveur)
• priority : 0 (never primary) permet de donner un ordre sur le futur
primary en cas de problèmes
• hidden : true permet de cacher le serveur des clients, il ne peut être
primary
• slaveDelay : Mets à jour les data avec un delay (ex : 8*3600 récupère les
données avec toujours 8h de retard) (rajouter hidden:true)
• vote : 2 (ex) permet de rajouter des votes (déconseiller, autant utiliser
arbiterOnly) [ex : Srv 1 (vote 2) Srv 2 (vote 1) si Srv tombe, Srv2 a 1/3, il
devient pas primary]

Replica set
Initialisation
# Use rs.initiate() on one and only one
member of the replica set:
> rs.initiate({
_id: "rs0",
version: 1,
members: [
{ _id: 0, host : "localhost:27017"
}
, { _id: 1, host :
"localhost:27018" }
]
}
)
# Add other replica:
> rs.add("localhost:27018")
> rs.addArb(" localhost :27019")
# Delete a server from the replicaSet:
> rs.remove("localhost:27018")
# Check the
configuration:
> rs.conf()

Replica set
Command
# In each Replica:
> rs.slaveOk()
# Check status:
> rs.status()
The secondary only accepts writes that it gets through replication.
To allow queries on a secondary, we must tell Mongo that we are okay with
reading from the secondary.

Replica set
Reconfiguration
# For the hidden:
> cfg = rs.conf()
> cfg.members[2].priority = 0
> cfg.members[2]. slaveDelay = 86400
> cfg.members[2].hidden = true
> rs.reconfig(cfg)
# For the hidden:
> rs.remove("localhost:27018")
> rs.addArb("localhost :27018")
To do only on the PRIMARY !

Fire & Forget strategy
You can configure MongoDB to fire-and-forget, sending off a write to the server without
waiting for an acknowledgment.
For high-volume, low-value data (like clickstreams and logs), fire-and-forget-style writes can be
ideal.
You can also configure MongoDB to guarantee that a write has gone to multiple replicas before
considering it committed. For important data, a safe mode setting is necessary.

TP – Replica set
1. Init 3 replicas.
2. Import the dump on the primary.
3. Put one of the replicas in backup, adjust its reception delay to 24h.
4. Try to insert data into a secondary.
5. Insert data into the primary and check its persistence on the network.
6. Add a fourth replica and configure it as an arbiter (check data behaviour on this one).
7. Import the file “place.json”. Is it persistent on all the network?
8. Set the priority to 2 for the primary, shutdown it and start it back.

TP – Replica set
# 1. Init 3 replica:
mongod --port 27017 --dbpath C:UsersalexaDocumentsCoursMongoDB2018-2019data1 --replSet rs0 --
mongo --port 27017
> rs.initiate()
> rs.conf()
mongo --port 27018
> rs.slaveOk()
mongo --port 27018
> rs.slaveOk()

TP – Replica set
# 2. Import the dump on the primary:
mongodump --archive --db crunchbase --port 27058 | mongorestore --archive --port 27017
# 3. Put one of the replicas in backup, adjust its reception delay to 24h:
> cfg = rs.conf()
> cfg.members[2].hidden = true
> rs.reconfig(cfg)
# 6. Add a fourth replica and configure it as an arbiter (check data behaviour on this one):
mongo --port 27017
> rs.addArb("localhost:27020")
mongo --port 27020
> rs.slaveOk()

TP – Replica set
# 7. Set the priority to 2 for the primary, shutdown it and start it back:
> cfg = rs.conf()
> rs.reconfig(cfg)

Aggregation

Aggregation
Swiss Army knife
Executes in native code
o Written in C++
o JSON parameter
Flexible, funcional, simple
o Operation pipeline
o Computational expressions

Aggregation
Operator Description
$match Filter documents
$project Reshape documents
$group Summarize documents
$unwind Expand arrays in documents
$sort Order documents
$limit / $skip Paginate documents
$redact Restrict documents
$geoNear Proximity sort documents
$let, $map Define variables

$match
# Matching field values
> {$match:{
language:"Russian"
}
{
title:"War and Peace",
pages:1440,
language:"Russian"
}
# Matching with query operators
> {$match:{
pages:{$gt:100}
}
{
title:"War and Peace",
pages:1440,
language:"Russian"
},
{
title:"Atlas Shrugged",
pages:1088,
language:"English"
}

$project
# Renaming and computing fields
> {$project:{
avgChapterLength:{
$divide:["$pages", "$chapters" ]
},
lang: "$language"
}}
{
_id:375,
avgChapterLength: 24,2222
lang:"English"
}
# Including & excluding fields
> {$project:{
_id:0,
title:1,
language:1
}}
{
title:"Great Gatsby" ,
language:"English"
}

$group
# Collect distinct values
> {$group:{
_id:"$langugage",
titles:{$addToSet:"$title"}
}}
{
_id:"English",
titles:["Atlas Shrugged" , "The
Great Gatsby"]
},
{
_id:"Russian",
titles:["War and Peace"]
}
# Calculating average, summing fields…
> {$group:{
_id:"$langugage",
pages:{$sum:"$pages"},
books:{$sum:1},
avgPages:{$avg:"$pages"}
}}
{
_id:"Russian",
pages:1440,
books:1,
avgPages:1440
}

$unwind
# Collect distinct values
> {$unwind:{
"subjects"
}
{
title:"The Great Gatsby",
ISBN:"9762832930920323" ,
subjects:"Long Island"
},
{
ISBN:"9762832930920323" ,
subjects:"New York"
},
{
ISBN:"9762832930920323" ,
subjects:"1920s"
}
{
ISBN:"9762832930920323" ,
subjects:[
"Long Island",
"New York",
"1920s"
]
}

TP - Aggregation
1. How many companies has more than 999 employees and was founded in or after 2000?
2. Number of companies and Number of employees group by founded year, ordrer by founded_year
desc?
3. How many companies group by category_code, with a list of all included companies names, with
category_code filter on medical or government?
4. How many companies has more than 1000 employees and was founded after 2000 (with agg.
function)?

TP - Aggregation
# 1. How many companies has more than 1000 employees and was founded after 2000?
> db.companies.count({$and:[{"number_of_employees":{$gte:1000}},{"founded_year":{$gte:2000}}]},{})
# 2. Number of companies and Number of employees group by founded year, order by founded_year desc?
> db.companies.aggregate ([
{ $sort : { founded_year: 1} },
{ "$group" : {
"_id" : "$founded_year",
"NumberOfCompanies" : {$sum : 1},
"NumberOfEmployees":{$sum : "$number_of_employees"}
}
}
]).pretty()

TP - Aggregation
# 3. How many companies group by category_code, with a list of all included companies names, with
category_code filter on medical or government?
{ "$match":{
category_code: {$in:["medical","government"]}
}
},
{ "$group" : {
"_id" : "$category_code",
"NumberOfCompanies" : {"$sum" : 1},
"Companies":{$addToSet:"$name"}
}
}
]).pretty()

TP - Aggregation
# 4. How many companies has more than 1000 employees and was founded after 2000 (with agg. function)?
{ "$match":{
$and:[{"number_of_employees":{$gte:1000}},{"founded_year":{$gte:2000}}]
}
},
{ "$group" : {
"_id" : null,
"NumberOfCompanies" : {"$sum" : 1}
}
}
]).pretty()
{ "$match":{
$and:[{"number_of_employees":{$gte:1000}},{"founded_year":{$gte:2000}}]
}
},
{ "$count" : "NumberOfCompanies" }
]).pretty()

Authentification

Authentication vs Authorization
Authentification Authorization
Verify the identity of
a user.
Verify the privileges of a
user.

Authentification
Client/User Auth
SCRAM-SHA-1
MONGODB-CR
X.509
LDAP
Kerberos
Internal Auth
Keyfile (SCRAM-SHA-1)
X.509
Community Enterprise

Authentification
BUSINESS NEEDS MONGODB SECURITY FEATURES
Authentication SCRAM, LDAP, Kerberos, x.509 Certificates
Authorization Built-in Roles, User-Defined Roles, Field-Level Redaction
Auditing Admin, DML, DDL, Role-Based
Encryption Network: SSL (with FIPS 140-2)
Disk : Encrypted Storage Engine or Partner Solutions

Localhost Exception
The localhost exception allows you to enable access control and then create the first user in the
system. With the localhost exception, after you enable access control, connect to the localhost
interface and create the first user in the admin database. The first user must have privileges to
create other users, such as a user with the userAdmin or userAdminAnyDatabase role.
Changed in version 3.0: The localhost exception changed so that these connections only have
access to create the first user on the admin database. In previous versions, connections that
gained access using the localhost exception had unrestricted access to the MongoDB instance.
The localhost exception applies only when there are no users created in the MongoDB instance
and only when you’re connected to database via the localhost interface, meaning in the same
server.

Client/User
Authentication
Mechanism
Mechanism Description
SCRAM-SHA-1
• Default mechanism
• Challenge / Response
• Username / Password
• IETF Standard
MONGODB-CR
• Challenge / Response
• Replaced by SCRAM-SHA-1
• Username / Password
• Deprecated as of MongoDB 3.0
X.509
• Certificate based
• Introduced in MongoDB 2.6
• TLS
LDAP
• Lightweight Director Access Protocol
• Used for directory information
• External authentication mechanism
Kerberos
• Developed at MIT
• Design for secure authentication
• External authentication mechanism

Client/User
Authentication
Initialisation
mongod --auth --dbpath C:UsersalexaDocumentsMongoDBdata
# Request:
> use admin
db.createUser(
{
user: "UserAdmin",
pwd: "abc123",
roles: [ { role: "userAdminAnyDatabase", db: "admin" } ]
}
)
The first thing you are allowed to do when connected to an
authenticated Mongo server is you’re allowed to create the firste user
in the database.
With that first user you create then create other users.

Client/User
Authentication
Authentification methods
After you’re created the first user in the database, the localhost exception will
not apply.
Always specify the database in which the user is created.
mongo admin --port 27017 -u "UserAdmin" -p "abc123"
OR:
mongo –port 27017 -u "UserAdmin" -p "abc123" –
authenticationDatabase=admin
> use admin
> db.auth(‘UserAdmin’, ‘abc123’ )
OR
When adding a user, you create the user in a specific database. This database is
the authentication database for the user.
A user can have privileges across different databases; i.e. a user’s privileges are
not limited to the authentication database. By assigning to the user roles in other
databases, a user created in one database can have permissions to act on other
databases.

Client/User
Authentication
Informations
# Returns users information:
> db.getUsers()
> db.system.users.find()
# Returns users information for a specified user:
> db.getUsers(username)

Client/User
Authentication
Role
Roles are grouped of privileges, actions over resources, that are granted to
users over a given namespace (database).
{
role: "<name>",
privileges: [
{ resource: { <resource> }, actions: [ "<action>", ... ] },
...
],
roles: [
{ role: "<role>", db: "<database>" } | "<role>",
...
]
}

Client/User
Authentication
Role

Client/User
Authentication
Role
All roles :
https://docs.mongodb.com/manual/reference/bui
lt-in-roles/
read : the role provides read access by granting the following actions
collStats
dbHash
dbStats
find
killCursors
listIndexes
listCollections

Client/User
Authentication
Action
Query & Write
find
Insert
remove
update
bypassDocumentValidationAll action:
https://docs.mongodb.com/manual/reference/
privilege-actions/06/06/2019 MongoDB class by Alexandre Bergere 147

Client/User
Authentication
Ressources
resource: {
db: "users"
, collection: "usersCollection"
,cluster: true
,anyResource: true
}

Client/User
Authentication
Role
> use admin
db.createRole(
{
role: "myClusterwideAdmin",
privileges: [
{ resource: { cluster: true }, actions: [ "addShard" ] },
{ resource: { db: "config", collection: "" }, actions: [
"find", "update", "insert", "remove" ] },
{ resource: { db: "users", collection: "usersCollection" },
actions: [ "update", "insert", "remove" ] },
{ resource: { db: "", collection: "" }, actions: [ "find" ] }
],
roles: [
{ role: "read", db: "admin" }
]
},
{ w: "majority" , wtimeout: 5000 }
)

Client/User
Authentication
Monitoring role
> use admin
db.createRole(
{
role: "manageOpRole",
privileges: [
{ resource: { cluster: true }, actions: [ "killop", "inprog" ]
},
{ resource: { db: "", collection: "" }, actions: [
"killCursors" ] }
],
roles: []
}
)
db.createRole(
{
role: "mongostatRole",
privileges: [
{ resource: { cluster: true }, actions: [ "serverStatus" ] }
],
roles: []
}
)

Client/User
Authentication
Role information
# Returns roles information:
> db.getRoles("read", {showPrivileges:true})
# Helpful:
> var readRoles = db.getRoles("read", {showPrivileges:true})
> readRoles.privileges[0]

Client/User
Authentication
Role modification
# Add a role:
> db.grantRolesToUser(
"reportsUser",
[
{ role: "read", db: "accounts" }
]
)
# Revoke a role:
> db.revokeRolesFromUser(
“myTester",
[
{ role: "readWrite", db: “crunchbase" }
]
)

Client/User
Authentication
User
# Create a new user and attribute role:
> db.createUser(
{
user: "myTester",
pwd: "xyz123",
roles: [ { role: "readWrite", db: "crunchbase" },
{ role: "read", db: "test" } ]
}
)

TP – Client/User Authentication
1. Create an admin user with the role “userAdminAnyDatabase” on the database “admin”.
2. Create a user “myTester” with a reader/writer role on the database “crunchbase”.
3. Create a user “Reader” with a reader role on the database “crunchbase.
4. Export the collection “artists”, delete it and import it back.

# 1. Create an admin user with the role “userAdminAnyDatabase” on the database “admin”.
mongod --auth --port 27017 --dbpath C:UsersalexaDocumentsCoursMongoDB2017-2018datadata
mongo
> use admin
> db.createUser(
{
user: "UserAdmin",
pwd: "abc123",
}
)

# 2. Create a user “myTester” with a reader/writer role on the database “crunchbase”.
mongo --port 27017 -u "UserAdmin" -p "abc123" --authenticationDatabase "admin"
OR
mongo
> use admin
> db.auth("UserAdmin", "abc123" )
> db.createUser(
{
user: "myTester",
pwd: "xyz123",
roles: [ { role: "readWrite", db: "crunchbase" } ]
}
)

# 3. Create a user “Reader” with a reader role on the database “crunchbase.
> db.createUser(
{
user: "myReader",
pwd: "xyz123",
roles: [ { role: "read", db: "crunchbase" } ]
}
)
# 4. Create a user “Reader” with a reader role on the database “crunchbase.
mongoexport -d crunchbase -c companies –out C:UsersalexaDocumentsMongoDBsrccompanies_export.json
mongoimport -d crunchbase -c companies -u "myTester" -p "xyz123" --authenticationDatabase "crunchbase"
C:UsersalexaDocumentsMongoDBsrccompanies.json

Internal
Authentication
Mechanism
Mechanism Description
Keyfile
(SCRAM-SHA-1)
• shared password
• copy exists on each member
• 6-1024 Base64 characters
• whitespace ignored
x.509
• certificate based
• recommended to issue different certs per member
Members of a replica set or sharded cluster must prove who they are.

Internal
Authentication
Shared / ReplicaSet authentication
With Keyfile access
1. Create a keyfile
Create a keyfile.
With keyfile authentication, each mongod instances in the replica set uses the
contents of the keyfile as the shared password for authenticating other members
in the deployment. Only mongod instances with the correct keyfile can join the
replica set.
2. Copy the keyfile to each replica set member
Copy the keyfile to each server hosting the replica set members. Ensure that the
user running the mongod instances is the owner of the file and can access the
keyfile.
3. Enable authentication for each member of the replica set.
openssl rand -base64 756 > <path-to-keyfile>
mongod --dbpath <path> --port <port> --replSet <replicaSetName> --fork
--keyFile <path-to-keyfile>
Update Existing Deployment

Internal
Authentication
With Keyfile access
4. Add first user
Add a user with the userAdminAnyDatabase role.
5. Authenticate as the user administrator
6. Create additional users as needed for your deployment
> use admin
> db.createUser(
{
user: "myUserAdmin",
pwd: "abc123",
}
)
> mongo --port 27017 -u "myUserAdmin" -p "abc123" --
authenticationDatabase "admin"
Update Existing Deployment
> db.createUser({
"user":"AdminCluster"
,"pwd":"password"
,roles:[{"role":"clusterAdmin","db":"admin"}]
})

Internal
Authentication
With Keyfile access
Follow replicaset & Update Existing Deployment.
OR
Or follow the link bellow: https://docs.mongodb.com/v3.0/tutorial/enable-internal-
authentication/ (Deploy New Replica Set with Access Control)
Deploy New Replica Set
with Access Control

Mongo DB Atlas

Mongo DB Atlas
DAAS : Database As A Service • Schema design
• Query and index optimization
• Server size selection - you must select the appropriate size of server,
coupled with IO and storage capacity
• Capacity planning - you must determine when you need additional
capacity, typically using the monitoring telemetry provided by
MongoDB Atlas, but you can make these changes with no downtime
• Initiating database restores
• How much you use

Mongo DB Cloud Manager

MongoDB Atlas vs MongoDB Cloud Manager
Feature Atlas Cloud Manager
Monitoring
Alert
API
Backup
Settings
Maintenance
Infrastructure

TP - MongoDB Atlas

Connector for bi

TP – Connector for bi
Follow the link : https://docs.mongodb.com/bi-connector/master

MongoDB

MongoDB & Hadoop

MongoDB & Spark

Mtools

Mtools
The following tools are in the mtools collection:
mlogfilter : Slices log files by time, merges log files, filters slow queries, finds table scans, shortens log lines, filters by
other attributes, convert to JSON
mloginfo : returns info about log file, like start and end time, version, binary, special sections like restarts,
connections, distinct view
mplotqueries : visualize log files with different types of plots (requires matplotlib)
mlogvis : creates a self-contained HTML file that shows an interactive visualization in a web browser (as an
alternative to mplotqueries)
mlaunch : a script to quickly spin up local test environments, including replica sets and sharded systems (requires
pymongo)

MongoDB Charts
MongoDB Charts is the fastest and
easiest way to build visualizations of
MongoDB data.
(beta)

Change Streams
More info.
Change streams allow applications to access real-time data changes without the complexity and risk of tailing the oplog.
Applications can use change streams to subscribe to all data changes on a collection and immediately react to them.

Stitch
Full access to MongoDB, declarative read/write
controls, and integration with your choice of services
MongoDB Stitch lets developers focus on building applications rather than on managing data manipulation code, service integration, or
backend infrastructure. Whether you’re just starting up and want a fully managed backend as a service, or you’re part of an enterprise and
want to expose existing MongoDB data to new applications, Stitch lets you focus on building the app users want, not on writing boilerplate
backend logic.

THE END

Support
MongoDB in action, 2nd Edition docs.mongodb.com

Summer Internship
https://www.mongodb.com/careers/college-students

Learning
https://www.university.mongodb.com

MongoDB classes 2019

Recommended

More Related Content

What's hot (20)

Similar to MongoDB classes 2019 (20)

Recently uploaded (20)

MongoDB classes 2019