Presentation 1
Presentation 1
2
Document
mongoD Database
B
3
2007
mongoD
B
4
2007
mongoD
B
Dwight Eliot Horowitz Kevin Ryan
Merriman
5
mongoDB 2007
Dwight
Merriman
Eliot Horowitz Kevin Ryan
Double Click
6
_id First_name Last_name E-mail Address Phone
1 Bipin Adhikari Bd@co Ktm 9823342
7
_id First_name Last_name E-mail Address Phone
1 Bipin Adhikari Bd@co Ktm 9823342
8
_id First_name Last_name E-mail Address Phone
1 Bipin Adhikari Bd@co Ktm 9823342
9
_id First_name Last_name E-mail Address Phone
1 Bipin Adhikari Bd@co Ktm 9823342
10
_idC First_name Last_name E-mail E-mail2 Address Phone Phone2
1 Bipin Adhikari Bd@co adk@co Ktm 9823342 963234
2 Bishow Thapa Bt@co kritipur 9833435
3 Krishna Mandal BKT 987364
4
5
6
7
8
9
10
11
12
{
“Key”: “Value”
“Key”:
mongoDB [“string”,123]
“key”:
{“key”:123}
}
{ {
“_id”:1, “_id”:2,
“first_name”: “bipin”, “first_name”:
“Last_name”:”adhikari “Bishow”,
:”, “Last_name”:”Thapa:”,
“email”; “email”; “bt@co”,
[“bd@co”,”adk@co”], “address”:Bkt
“address”:ktm “phone”:
“phone”: [971726,9812372]
“
[9873726,987372] }
} DATA ACCESSED
TOGETHER, STAYS
TOGETHER
” 13
{
“Key”: “Value”
“Key”:
mongoDB [“string”,123]
“key”:
{“key”:123}
}
{ {
“_id”:1, “_id”:2,
“first_name”: “bipin”, “first_name”:
“Last_name”:”adhikari “Bishow”,
:”, “Last_name”:”Thapa:”,
“email”; “email”; “bt@co”,
[“bd@co”,”adk@co”], “address”:Bkt
“address”:ktm “phone”:
“phone”: [971726,9812372]
“
[9873726,987372] }
} DATA ACCESSED
TOGETHER, STAYS
TOGETHER
” 14
MongoDB SQL
Document Tuple
Collection Table and View
Primary Key: _ID field Primary Key: Any column
Uniformity is not required. It has a Uniformity relational
Schema.
Index Index
Embedded Structure Joins
CRUD DML
Horizontal Scalability Vertical Scalability
Schema Dynamic Schema Predefined
15
Why MongoDB?
16
Key Value
1933287 Acer Nitro 5
1982373 Fantech Mouse
1827323 Keyboard72
1827346 Hand sanitizer
17
Key Hash Value
1933287 23 Acer Nitro 5
1982373 18 Fantech Mouse
1827323 59 Keyboard72
1827346 100 Hand sanitizer
0 50 100
18
Performance chart of SQL and
MongoDB
50
40
30
20
10
0
50 500 5000 25000 50000
mongodb sql 19
Pros
1. There is no Downtime needed in the case of
Application scalability.
2. MongoDB can perform in-memory processing.
3. Capable to perform the text-based search operation.
4. MongoDB can perform Graph processing.
5. It is very Economical.
6. Global replication.
20
21
Cons
MongoDB is not good for the below implementation.
1. Not suitable for high transaction operation.
2. There is no support for the ACID principle.
3. The complex SQL in which many joins are present.
4. The system in which the data model is developed
upfront.
22