#LifeKoKaroLift

SGC Coaching:
Articulate your Journey | Activate Students’ Vigour| Accelerate Mutual Growth

JumpStart to an engaging session with

your group!
using these slides for reference
Agenda

Introduction (10 mins)

Focused Teaching (60 mins)

Doubt Resolution (20 mins)

 Why NOSQL
 Support large numbers of concurrent users (tens of thousands, perhaps millions)

 Deliver highly responsive experiences to a globally distributed base of users

 Be always available – no downtime

 Handle semi- and unstructured data

 Rapidly adapt to changing requirements with frequent updates and new features

 Provide flexible schemas that enable faster and more iterative development.

 Designed to scale out by using distributed clusters of hardware instead of scaling up by

adding expensive and robust servers.

 Optimized for specific data models and access patterns that enable higher performance
than trying to accomplish similar functionality with relational databases.
Concept / Logical model Definition
Theory of noSQL: CAP
Many nodes
Nodes contain replicas of partitions of data
C
Consistency

• all replicas contain the same version of

data
Availability

• system remains operational on failing

nodes
Partition tolarence A P
• multiple entry points CAP Theorem:
• system remains operational on system
split
satisfying all three at the
same time is impossible
Why MongoDB?
• Rich Object Model: MongoDB supports a rich and expressive object model. Objects can have
properties and objects can be nested in one another (for multiple levels).

• Secondary Indexes: Indexes speed up the queries significantly, but they also slow down writes.
Secondary indexes are a first-class construct in MongoDB. This makes it easy to index any
property of an object stored in MongoDB even if it is nested.

• Replication and high availability: MongoDB supports a "single master" model. This means you
have a master node and several slave nodes. In case the master goes down, one of the slaves is
elected as master

• Native Aggregation: MongoDB has a built-in Aggregation framework to run an ETL(Extract,

transform and load) pipeline to transform the data stored in the database.

• Schema-less Models: MongoDB, allows you to not enforce any schema on your documents.
While this was the default in prior versions, in the newer version you have the option to enforce a
schema for your documents.
RDBMS vs MongoDB
 Use case

In MongoDB design the Actor and Category

are nested into Film

• A films could be acted by multiple actors and

actresses.
• A film can belong to multiple categories.
• An actor or actress could act multiple films.
• A category could include multiple films.
MongoDB shell demo
References

https://docs.mongodb.com/guides/server/read_queries/

https://docs.mongodb.com/mongodb-shell/install/
Personalized Feedback and Doubt resolution

Doubt Resolution

Questions??