Scribd
Upload
33 views15 pages

Nosql: Under The Guidence of P.Ramesh Babu

This document provides an overview of NoSQL databases. It discusses how the rise of web-based applications and large datasets led to the development of NoSQL as an alternative to relational databases. NoSQL databases are non-relational, do not require fixed schemas, and relax ACID properties. The two main types are key-value stores and schema-less databases. NoSQL provides advantages like horizontal scaling, replication, and high performance for large datasets.

Uploaded by

Virat Sandeep
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
33 views15 pages

Nosql: Under The Guidence of P.Ramesh Babu

This document provides an overview of NoSQL databases. It discusses how the rise of web-based applications and large datasets led to the development of NoSQL as an alternative to relational databases. NoSQL databases are non-relational, do not require fixed schemas, and relax ACID properties. The two main types are key-value stores and schema-less databases. NoSQL provides advantages like horizontal scaling, replication, and high performance for large datasets.

Uploaded by

Virat Sandeep
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 15

NoSQL

UNDER THE GUIDENCE OF


P.RAMESH BABU

PRESENTED BY
P.SAI KRISHNA
History of the World, Part 1

 Relational
Databases – mainstay of business
 Web-based applications caused spikes
– Especially true for public-facing e-Commerce sites
 Developers begin to front RDBMS with memcache or
integrate other caching mechanisms within the
application (ie. Ehcache)

2
What is NoSQL?

 Stands for Not Only SQL


 Class of non-relational data storage systems
 Usually do not require a fixed table schema nor do
they use the concept of joins
 All NoSQL offerings relax one or more of the ACID
properties (will talk about the CAP theorem)

3
Why NoSQL?

 For data storage, an RDBMS cannot be the be-


all/end-all
 Just as there are different programming languages,
need to have other data storage tools in the toolbox
 A NoSQL solution is more acceptable to a client now
than even a year ago
– Think about proposing a Ruby/Rails or Groovy/Grails
solution now versus a couple of years ago

4
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 (Ruby/Groovy), a shift to
dynamically-typed data with frequent schema
changes
 Open-source community

5
Dynamo and BigTable

 Three
major papers were the seeds of the NoSQL
movement
– BigTable (Google)
– Dynamo (Amazon)
• Gossip protocol (discovery and error detection)
• Distributed key-value data store
• Eventual consistency
– CAP Theorem (discuss in a sec ..)

6
The Perfect Storm

 Large datasets, acceptance of alternatives, and


dynamically-typed data has come together in a
perfect storm
 Not a backlash/rebellion against RDBMS
 SQL is a rich query language that cannot be rivaled
by the current list of NoSQL offerings

7
What kinds of NoSQL

 NoSQL solutions fall into two major areas:


– Key/Value or ‘the big hash table’.
• Amazon S3 (Dynamo)
• Voldemort
• Scalaris
– Schema-less which comes in multiple flavors,
column-based, document-based or graph-
based.
• Cassandra (column-based)
• CouchDB (document-based)
• Neo4J (graph-based)
• HBase (column-based)

8
Key/Value

Pros:
– very fast
– very scalable
– simple model
– able to distribute horizontally

Cons:
- many data structures (objects) can't be easily
modeled as key value pairs

9
Common Advantages

 Cheap, easy to implement (open source)


 Data are replicated to multiple nodes (therefore identical
and fault-tolerant) and can be partitioned
– Down nodes easily replaced
– No single point of failure
 Easy to distribute
 Don't require a schema
 Can scale up and down
 Relax the data consistency requirement (CAP)

10
Some Statistics

 FacebookSearch
 MySQL > 50 GB Data
– Writes Average : ~300 ms
– Reads Average : ~350 ms
 Rewritten with Cassandra > 50 GB Data
– Writes Average : 0.12 ms
– Reads Average : 15 ms

11
Some things to think about

 Ruby on Rails and Grails have ORM baked in. Would


have to build your own ORM framework to work with
NoSQL.
– Some plugins exist.
 Same would go for Java/C#, no Hibernate-like
framework.
– A simple JDO framework does exist.
 Support for basic languages like Ruby.

12
Some more things to think about

 Troubleshooting performance problems


 Concurrency on non-key accesses
 Are the replicas working?
 No TOAD for Cassandra
– though some NoSQL offerings have GUI tools
– have SQLPlus-like capabilities using Ruby IRB
interpreter.

13
Questions

14
THANK YOU

15

You might also like