TOPIC-Introduction to

NoSQL

Big data
Name-Ajay Kushwaha
Roll no.-2000290110017

1
NoSQL!
NoSQL databases are currently a hot topic in some parts of
computing, with over a hundred
different NoSQL databases.
No SQL?

• NoSQL stands for:

• No Relational
• No RDBMS
• Not Only SQL
• NoSQL is an umbrella term for all databases and data stores
that don’t follow the RDBMS principles
• A class of products
• A collection of several (related) concepts about data storage and manipulation
• Often related to large data sets
 NoSQL Definition
From www.nosql-database.org:
Next Generation Databases mostly
addressing some of the points: being
non-relational, distributed, open-
source and horizontal scalable. The
original intention has been modern
web-scale databases. The movement
began early 2009 and is growing
rapidly. Often more characteristics
apply as: schema-free, easy replication
support, simple API, eventually
consistent / BASE (not ACID), a huge
data amount, and more.
Where does NoSQL come from?

• Non-relational DBMSs are not new

• But NoSQL represents a new incarnation
• Due to massively scalable Internet applications
• Based on distributed and parallel computing
• Development
• Starts with Google
• First research paper published in 2003
• Continues also thanks to Lucene's developers/Apache (Hadoop) and Amazon
(Dynamo)
• Then a lot of products and interests came from Facebook, Netfix, Yahoo,
eBay, Hulu, IBM, and many more
Dynamo and BigTable

• Three major papers were the seeds of the NoSQL movement

• BigTable (Google)
• Dynamo (Amazon)
• Distributed key-value data store
• Eventual consistency
• CAP Theorem (discuss in a sec ..)
NoSQL and Big Data

• NoSQL comes from Internet, thus it is often related to the

“big data” concept
• How much big are “big data”?
• Over few terabytes Enough to start spanning multiple storage units
• Challenges
• Efficiently storing and accessing large amounts of data is difficult, even more
considering fault tolerance and backups
• Manipulating large data sets involves running immensely parallel processes
• Managing continuously evolving schema and metadata for semi-structured
and un-structured data is difficult
How did we get here?

• Explosion of social media sites (Facebook, Twitter) with

large data needs
• Rise of cloud-based solutions such as Amazon S3
(simple storage solution)
• Just as moving to dynamically-typed languages (Python,
Ruby, Groovy), a shift to dynamically-typed data with
frequent schema changes
• Open-source community
Why are RDBMS not suitable for Big Data

• The context is Internet

• RDBMSs assume that data are
• Dense
• Largely uniform (structured data)
• Data coming from Internet are
• Massive and sparse
• Semi-structured or unstructured
• With massive sparse data sets, the typical storage
mechanisms and access methods get stretched
 NoSQL Distinguishing Characteristics
• Large data volumes • Asynchronous Inserts &
• Google’s “big data” Updates
• Scalable replication • Schema-less
and distribution • ACID transaction
• Potentially thousands of properties are not needed –
machines BASE
• Potentially distributed • CAP Theorem
around the world • Open source development
• Queries need to return
answers quickly
• Mostly query, few
updates
NoSQL Database Types

Discussing NoSQL databases is complicated

because there are a variety of types:

•Sorted ordered Column Store

•Optimized for queries over large datasets, and store
columns of data together, instead of rows
•Document databases:
•pair each key with a complex data structure known as a document.
•Key-Value Store :
•are the simplest NoSQL databases. Every single item in the database is stored as an
attribute name (or 'key'), together with its value.
•Graph Databases :
•are used to store information about networks of data, such as social connections.
Document Databases (Document Store)

• Documents
• Loosely structured sets of key/value pairs in documents, e.g., XML, JSON,
BSON
• Encapsulate and encode data in some standard formats or encodings
• Are addressed in the database via a unique key
• Documents are treated as a whole, avoiding splitting a document into its
constituent name/value pairs
• Allow documents retrieving by keys or contents
• Notable for:
• MongoDB (used in FourSquare, Github, and more)
• CouchDB (used in Apple, BBC, Canonical, Cern, and more)
Document Databases (Document Store)

• The central concept is the notion of a "document“ which corresponds to a

row in RDBMS.
• A document comes in some standard formats like JSON (BSON).
• Documents are addressed in the database via a unique key that represents
that document.
• The database offers an API or query language that retrieves documents
based on their contents.
• Documents are schema free, i.e., different documents can have structures
and schema that differ from one another. (An RDBMS requires that each
row contain the same columns.)

13
 Document Databases, JSON
{
_id: ObjectId("51156a1e056d6f966f268f81"),
type: "Article",
author: "Derick Rethans",
title: "Introduction to Document Databases with MongoDB",
date: ISODate("2013-04-24T16:26:31.911Z"),
body: "This arti…"
},
{
_id: ObjectId("51156a1e056d6f966f268f82"),
type: "Book",
author: "Derick Rethans",
title: "php|architect's Guide to Date and Time Programming with PHP",
isbn: "978-0-9738621-5-7"
}
Key/Value stores
• Store data in a schema-less way
• Store data as maps
• HashMaps or associative arrays
• Provide a very efficient average running
time algorithm for accessing data
• Notable for:
• Couchbase (Zynga, Vimeo, NAVTEQ, ...)
• Redis (Craiglist, Instagram, StackOverfow,
flickr, ...)
• Amazon Dynamo (Amazon, Elsevier,
IMDb, ...)
• Apache Cassandra (Facebook, Digg,
Reddit, Twitter,...)
• Voldemort (LinkedIn, eBay, …)
• Riak (Github, Comcast, Mochi, ...)
Sorted Ordered Column-Oriented Stores
• Data are stored in a column-oriented way
• Data efficiently stored
• Avoids consuming space for storing nulls
• Columns are grouped in column-families
• Data isn’t stored as a single table but is stored by column families
• Unit of data is a set of key/value pairs
• Identified by “row-key”
• Ordered and sorted based on row-key

• Notable for:
• Google's Bigtable (used in all
Google's services)
• HBase (Facebook, StumbleUpon,
Hulu, Yahoo!, ...)
Scaling RDBMS

• Master-Slave
• All writes are written to the master. All reads performed against
the replicated slave databases
• Critical reads may be incorrect as writes may not have been
propagated down
• Large data sets can pose problems as master needs to duplicate
data to
• Sharding
• Any DB distributed across multiple machines needs to
know in what machine a piece of data is stored or must be
stored
• A sharding system makes this decision for each row, using
its key
NoSQL, No ACID

• RDBMSs are based on ACID (Atomicity, Consistency,

Isolation, and Durability) properties
• NoSQL
• Does not give importance to ACID properties
• In some cases completely ignores them
• In distributed parallel systems it is difficult/impossible to
ensure ACID properties
• Long-running transactions don't work because keeping resources
blocked for a long time is not practical
Performance
• There is no perfect NoSQL database
• Every database has its advantages and disadvantages
• Depending on the type of tasks (and preferences) to accomplish
• NoSQL is a set of concepts, ideas, technologies, and software
dealing with
• Big data
• Sparse un/semi-structured data
• High horizontal scalability
• Massive parallel processing
• Different applications, goals, targets, approaches need
different NoSQL solutions
 Where would I use it?

• Where would I use a NoSQL database?

• Do you have somewhere a large set of uncontrolled, unstructured,
data that you are trying to fit into a RDBMS?
• Log Analysis
• Social Networking Feeds (many firms hooked in through Facebook or
Twitter)
• External feeds from partners
• Data that is not easily analyzed in a RDBMS such as time-based data
• Large data feeds that need to be massaged before entry into an
RDBMS