Downloaded 35 times
![Relational MongoDB
id hero game
0 Commander Shepard Mass Effect
1 Hawke Dragon Age
id name type hero_id
0 Sniper rifle Ranged combat 0
1 Daggers Melee combat 1
2 Stealth Class skill 1
3 Tactical cloak Class skill 0
HERO
SKILL
{
_id: <ObjectID>,
name: “Commander Shepard”,
game: “Mass Effect”,
skills: [{
name: “Sniper rifle”,
type: “Ranged combat”,
}, {
name: “Tactical cloak”,
type: “Class skill”,
}]
}
HERO](https://image.slidesharecdn.com/introductiontomongodb-170519140936/85/Introduction-to-MongoDB-17-320.jpg)
![MongoDB Documents are Typed
{
name : “J. Shepard”,
title : “Commander”,
Address : {
address1:
“Tiberius Tower”,
address2:
“Citadel”,
pincode : “11E
SR2”,
}
expertise: [ “Sniper”, “Combat”, “Tech”, “Reapers”],
employee_number : 320,
}](https://image.slidesharecdn.com/introductiontomongodb-170519140936/85/Introduction-to-MongoDB-18-320.jpg)
![Find
db.games.find(
{ year: “2007” },
{ name: 1, publisher: 1, _id: 0 }
)
Result:
[{
name: “Mass Effect”,
publisher: “BioWare”
}]](https://image.slidesharecdn.com/introductiontomongodb-170519140936/85/Introduction-to-MongoDB-21-320.jpg)
Uploaded byNodeXperts
Introduction to MongoDB
The document provides an introduction to MongoDB, explaining it as an open-source document-oriented NoSQL database that contrasts with traditional SQL databases. It covers concepts such as the document data model, CRUD operations, and the benefits and drawbacks of using MongoDB, including its schema-less design and fast scalability. Additionally, it outlines when to use or not use MongoDB based on application requirements.
More Related Content
Similar to Introduction to MongoDB
Introduction to MongoDB
- 1. Introduction to MongoDB Get startedon your way to being a NoSQL Ninja!
- 2.
- 3.
- 4.
- 5. Points of Discussion Whatis MongoDB? SQL vs NoSQL Document Data Model CRUD operations Cursor concepts Benefits & drawbacks Use cases & “Don’t Use!” cases
- 6.
- 7. What is MongoDB? Open-source Document-oriented NoSQLdatabase But what is NoSQL? - Alternative mechanism for data storage - Addresses challenges faced by SQL databases
- 8. DOCUMENT Basic unit ofdata in MongoDB Analogous to row in relational database Obtained as JSON object Exists on disk as BSON
- 9. COLLECTION Group of documents Analogousto table in relational database Does not enforce a schema Documents in a collection usually have similar purpose
- 10. DATABASE Container for collections Storesfiles on disk A single MongoDB server usually has multiple databases Collection 1 Collection 3 Collection 2 Collection 4
- 11.
- 12. Differences between SQL& NoSQL SQL NoSQL Table-based Document or key-value pair based Predefined schema Dynamic schema, or no schema Vertically scalable Horizontally scalable
- 13. Differences between SQL& NoSQL SQL NoSQL Better for relational data Better for hierarchical data Better for transactions Better for faster IO Examples: MySql, Oracle, MS-SQL etc Examples: MongoDB, CouchDB, RethinkDB etc
- 14.
- 15.
- 16.
- 17. Relational MongoDB id herogame 0 Commander Shepard Mass Effect 1 Hawke Dragon Age id name type hero_id 0 Sniper rifle Ranged combat 0 1 Daggers Melee combat 1 2 Stealth Class skill 1 3 Tactical cloak Class skill 0 HERO SKILL { _id: <ObjectID>, name: “Commander Shepard”, game: “Mass Effect”, skills: [{ name: “Sniper rifle”, type: “Ranged combat”, }, { name: “Tactical cloak”, type: “Class skill”, }] } HERO
- 18. MongoDB Documents areTyped { name : “J. Shepard”, title : “Commander”, Address : { address1: “Tiberius Tower”, address2: “Citadel”, pincode : “11E SR2”, } expertise: [ “Sniper”, “Combat”, “Tech”, “Reapers”], employee_number : 320, }
- 19.
- 20. Insert db.games.insert( { name: “Mass Effect”, year:“2007”, publisher: “BioWare” } )
- 21. Find db.games.find( { year: “2007”}, { name: 1, publisher: 1, _id: 0 } ) Result: [{ name: “Mass Effect”, publisher: “BioWare” }]
- 22. Update db.games.update( { year: “2007”}, { $set: { publisher: “EA” } }, { multi: true } ) Updated Document: { name: “Mass Effect”, year: “2007” publisher: “EA” }
- 23.
- 24.
- 25. Cursor A pointer tothe result set of a query Clients can iterate through a cursor to retrieve results The find queries we saw before return a cursor by default: db.games.find({ year: “2007” }) a cursor
- 26. Cursor Iteration Calling cursor.next()returns the next document Cursor points to each document in the results MongoDB result as set of documents Now let’s see some cursor operations.
- 27. Count Returns the totalnumber of results in a cursor. Example: db.games.find( { year: “2007” } ).count()
- 28. Sort Sorts the resultsof a cursor based on given key and order. Example: db.games.find({}).sort( { year: -1 } ) sort criteria
- 29. Limit Limits the resultsof a cursor based on given number. Example: db.games.find( { year: “2007” } ).limit(5)
- 30. Skip Specifies the offsetfor returning results. Example: db.games.find( { year: “2007” } ).skip(5)
- 31.
- 32. Atomicity & Transactions MongoDB: Supportsatomicity within a single document Does not support transactions or rollbacks If your application requires transactions: - Use a relational database for that part of operations
- 33. Benefits of MongoDB Schema-lessdesign Cost effectiveness Quick start & fast learning Replica sets Auto Sharding Strong community Rapidly evolving technology
- 34. Drawbacks of MongoDB Noautomatic joins No transactions Chances of data inconsistency are slightly higher Data size in MongoDB is typically higher
- 35. When to useMongoDB Real time application Need for fast I/O Storing data with little to no structure Fast scaling required Rapid development
- 36. When to notuse MongoDB Data has a lot of relations ACID compliancy is needed (Atomicity, Consistency, Isolation, Durability) Transactions and rollbacks are needed Data is structured and unchanging
- 38. THANK YOU ! ANYQUESTIONS?