NoSQL Database ppt for Beginners by Real Time Expert

Introduction to
NOSQL
Email: sales@kerneltraining.com
Call us: +91 8099776681

www.kerneltraining.com
Market Needs
 According to market survey it required :
 Database capable to handle Explosion of social media sites (Facebook, Twitter)
with large data needs
 Explosion of storage needs in large web sites such as Google, Yahoo
 Required database who can work on clusters
 Database who is capable to tune with 21st cent
 Ury websites( e. g. schema less, with out large relations, mostly for open source ).

Market Forecast

Market Top 10 Ranking

Seeing the future
In future database popularity

Why No SQL ?
 Its easy and ready to manage with clusters .
 Suitable for upcoming data explosions .
 Not required to keep track with data structure.
 provide easy and flexible system .

Smooth process of No SQL

Upcoming Job trends

Salary hike

What is No SQL
 No SQL means Not Only SQL, implying that
when designing a software solution or product, there
are more than one storage mechanism that could be
used based on the needs.
 The most important result of the rise of NoSQL
is Polyglot Persistence.

Database Scaling
 RDBMS are "scaled up" by adding hardware
 processing power
 No SQL is "scaled out" by spreading the load
 Partitioning /replication App
Load
balancer
User
A-K
User
L-O
User
P-S
User
A - Z

Relational DB Scaling
At certain point relational database won't scale

No SQL DB Scaling
At certain point relational database won't scale

Characteristics
 NoSQL databases share some characteristics
with respect to scaling and performance:
o Auto sharding
o Distributed query support
o Integrated caching

Where NoSQL Is Used?
 Google (BigTable, LevelDB)
 LinkedIn (Voldemort)
 Facebook (Cassandra)
 Twitter (Hadoop/Hbase, FlockDB, Cassandra)
 Netflix (SimpleDB, Hadoop/HBase, Cassandra)
 CERN (CouchDB

History of NoSQL
oMultiValue databases at TRW in 1965.
o DBM is released by AT&T in 1979.
o Lotus Domino released in 1989.
o Carlo Strozzi used the term NoSQL in 1998 to name his lightweight,
oopen-source relational database that did not expose the standard SQL
interface.
oGraph database Neo4j is started in 2000.
oGoogle BigTable is started in 2004. Paper published in 2006.
o CouchDB is started in 2005.
o The research paper on Amazon Dynamo is released in 2007.
o The document database MongoDB is started in 2007 as a part of a open
osource cloud computing stack and first standalone release in 2009.
oFacebooks open sources the Cassandra project in 2008.
oProject Voldemort started in 2008.
oThe term NoSQL was reintroduced in early 2009.

cap theorem 1/2
The need for scaling up/down/out is growing and so are the challenges of
dealing with huge distributed systems. So, when designing such applications,
it’s important to keep three core requirements in mind as described by
Brewer’s CAP theorem:
1. Consistency
2. Availability
3. Partition-Tolerance
A distributed system can satisfy any two of these
Guarantees at the same time, but not all three

Cap theorem 2/2
 In other words, CAP can be expressed as "If the network is broken, your
database won’twork"
 In RDBMS we do not have P (network partitions)
 ○ Consistency and Availability are achieved
 In No SQL we want to have P
 Need to select either C or A
 Drop A -> Accept waiting until data is consistent
 Drop C -> Accept getting inconsistent data
sometimes

No sql system and cap

ACID vs BASE
Scalability and better performance of No SQL is
achieved by sacrificing ACID compatibility.
Atomic, Consistent, Isolated, Durable
No SQL is having BASE compatibility instead.
Basically Available, Soft state,
Eventual consistency

No SQL dose not use SQL
 Sql was designed to be a query language for relational
database .
 Relational databases are usually table based . Mush like a
spread- sheet .
 records are stored in row and column management .

No SQL are more flexible
 Many of No SQL databases allow the definition of fields
on record creation .
 Nested values are common in No SQL database.
 Fields are not standardizes between records .

Types of No SQL databases
NoSQL
DataTypes
Key Value
store
Example
Riak, Amazon
S3 (Dynamo)
Document
Based store
Example
CouchDB
Column based
store
Example
HBase,
Cassandra
Graph based
Example -
Neo4J

Descriptions about Document Based
 Document based
 Documents are usually stored in a structured format.
 Documents are usually organized into collections or databases.
 Individual document can have unique structure .
 Each document has a specific key .
 Examples – json , Bson , XML

Key Value
 You have a key and you can query by , and value at that by .
 Not possible to query by other then a key .
 Sometimes used alongside relational databases for caching .

Column Based
 Each row in a tabular database can have a different set of
columns.
 Tabular databases are designed for large numbers of columns
in each row, and rows are typically versioned .

Graph Based
 These databases that uses edges and nodes to represent and
store data.
 These nodes are organised by some relationships with one
another, which is represented by edges between the nodes.
 Both the nodes and the relationships have some defined
properties.

Questions?

THANK YOU
for attending Demo of
NOSQL
Email: sales@kerneltraining.com
Call us: +91 8099776681

NoSQL Database ppt for Beginners by Real Time Expert

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (10)

Recently uploaded

Recently uploaded (20)

NoSQL Database ppt for Beginners by Real Time Expert