The document discusses NoSQL databases, highlighting their scalability, flexibility, and types such as key-value, column store, document store, and graph databases. It outlines a multi-step decision-making process for selecting the appropriate database, including evaluating use cases, analyzing system features, and considering business needs. Additionally, it mentions industry use cases for NoSQL, such as IoT and social network analysis.

2. Say Yes to NoSQL
Dr. Rohit Kumar

3. Evolution of data

4. Some Interesting Facts About Data

5. What Is NoSQL
NoSQL
Scalable Fast Flexible and Easy

6. SQL to NoSQL

7. Source: https://olive4oyl.wordpress.com/2016/08/31/sql-vs-nosql/

8. Types Of NoSQL
Types Performance Scalability Flexibility Complexity Example
Key-Value high high high None Riak, redis,
Column Store high high Moderate Low Hbase, Google
big Table,
Cassandra
Document Store high Variable(high) high Low MongoDB,
Couchbase
Graph Database Variable Variable high high Neo4J

9. How To Decide??
• Step 1
Read about the various Type and how they work.

10. How To Decide??
• Step 2
Investigate all the use cases for your project. This will help to
identify which all type you need. Remember it could be a
mixed solution.

11. How To Decide??
• Step 3
Check the ranking and popularity of the selected type of
system. Analyze the pros and cons as per your requirement.

12. How To Decide??
Step 4 (as an expert)
•Can the database serve as the primary data source for the online application?
•Does the database have features that prevent the loss of critical data? Are writes
durable in nature by default so that the data is safe?
•Is the database fault-tolerant, and is it capable of providing continuous
availability?
•Can the database easily replicate data located in the same data center, across
multiple data centers, and across different cloud availability zones?
•Does the database offer read/write anywhere capabilities? (Can any node in the
cluster be written to and read from?)
•Does the database provide a robust set of security features?
Source: https://support.rackspace.com/how-to/choosing-between-rdbms-and-nosql/

13. How To Decide??
Step 4 (as an expert)
•Does the database support backup and recovery procedures that are easy to
create and manage?
•Does the database require special caching layers?
•Is the database capable of managing big data and delivering high performance
regardless of data size?
•Does the database offer linear scalability for adding new nodes?
•Can new nodes be added and removed online without impacting your business?
•Does the database support key platforms and developer languages?
•Does the database provide a query language that is similar to SQL?
Source: https://support.rackspace.com/how-to/choosing-between-rdbms-and-nosql/

14. How To Decide??
Step 4 (as an expert)
•Can the database run on commodity hardware with no special requirements?
•Is the database easy to implement and maintain for large deployments?
•Does the database offer data compression that results in significant storage savings?
•Is it easy to run analytic operations on the database?
•Can the database easily interface with and support modern data warehouses or data lakes
that use Hadoop?
•Is it easy to carry out search operations and functions directly on the NoSQL database?
•Can the database isolate the online, analytic, and search workloads within a single
application?
•Does the database have solid command-line and visual tools for development,
administration, and performance management?
Source: https://support.rackspace.com/how-to/choosing-between-rdbms-and-nosql/

15. How To Decide??
• Is Technical Consideration Enough?
Think about the business need. Such as Community support, Enterprise
fee, commercial Support, Documentation.

16. How To Decide?
• Finally resource and deployment needs.

17. Some Industry Use Case for NoSQL
• IoT
• Social network Analysis

18. Thank You