Sql vs nosql

April 18, 2023

SQL vs. NoSQLMaking the right choice

© Copyright Dimension Data 218 April 2023

The contenders

SQL NoSQL

http://www.google.be/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&docid=ejK2kNhrs1imkM&tbnid=ItihwXdKCTv8aM:&ved=0CAUQjRw&url=http://sqlmag.com/database-performance-tuning/best-sql-server-database-monitoring-performance-product-2013&ei=8S4DVMz3OInAPLKggbgN&bvm=bv.74115972,d.ZGU&psig=AFQjCNG4-otuk8Dp91odQITrDMDoSJF68g&ust=1409581143332098


SQL Databases

• RDBMS

• Standardized

• Mature

• Reliable

• Well understood

• Queryable

• ACID


NoSQL scalability argument

• Scale-Up vs Scale-Out• Use of commodity hardware

• Locking / Latching

• Consistency over partitions

• Availability of partitions

• Referential integrity

Se-ries1

Cost of scaling

SQL NoSQL


Other RDBMS / SQL Database drawbacks

• One-solution-fits-all• Slow for certain tasks

• ACID is not always needed

• ORM required

• Lack of flexibility• Rigid schema

• Management complexity

• Add-on solutions• XML-fields, Filestreams

• Full-text indexes


CAP theorem (Brewer's theorem)


NoSQL Use Cases

• Bigness / Avoid hitting the wall

• Massive write performance

• Write availability

• Fast key-value access

• Flexible schema and flexible datatypes

• Schema migration

• No single point of failure

• Generally available parallel computing

• Easier maintainability, administration and operations

• Programmer ease of use

• Use the right data model for the right problem

• Tunable CAP tradeoffs


ACID Transactions

Atomicity

Consistancy

Isolation

Durability


NoSQL ACID Trade-offs

• Dropping Atomicity lets you shorten the time tables (sets of data) are locked. MongoDB, CouchDB.

• Dropping Consistency lets you scale up writes across cluster nodes.Riak, Cassandra.

• Dropping Durability lets you respond to write commands without flushing to disk.Memcache, Redis.


NoSQL Database Main Types

• Key-Value Store• A basic dictionary design storing values under unique keys

• The database does not care about the structure of the value

• Examples:

• Memcache

• Riak

• Azure Blob Storage

• Good at:

• Handles size well

• Processing a constant stream of small reads and writes

• Fast

• Programmer friendly



• Column Store• A column is a tuple of 3 elements: unique name of value, a typed

value, timestamp

• Columns may be part of column families

• Columns need not appear in every record

• Example:

• Hbase

• Hypertable

• Cassandra

• Azure Table Storage

• Good at:

• Handles size well

• Stream massive write loads

• High availability

• Multiple-data centers

• MapReduce.



• Document Store• Use a unique key to store and retrieve a JSON document

• Documents are schemaless

• Metadata is added to the document to aid querying

• Indexing of documents and metadata speeds up retrieval

• Example:

• CouchDB

• MongoDB

• RavenDB

• Azure DocumentDB service (Preview)

• Good at:

• Natural data modeling

• Programmer friendly

• Rapid development

• Web friendly

• CRUD



• Graph Database• Uses graph structures with nodes, edges, and properties to represent

and store data

• Every element contains a direct pointer to its adjacent elements

• Example:

• AllegroGraph

• InfoGrid

• Neo4j

• Good at:

• Complicated graph problems

• Topographical data

• Fast


NoSql Database Type Comparison

Data Model Performance Scalability Flexibility Complexity Functionality

Key–Value Store

high high high none variable (none)

Column-Oriented Store

high high moderate low minimal

Document-Oriented Store

high variable (high) high low variable (low)

Graph Database

variable variable high high graph theory

Relational Database

variable variable low moderaterelational algebra


Things to consider when choosing

• Where are you starting from?

• What are you trying to accomplish?

• Things to Consider...• Your Problem

• Access pattern, scalability, consistency, durability

• Money

• Scaling, admins, license, operating cost

• Programming

• Flexible schema, JSON, REST, language, graphs

• Performance

• Reads, writes, consistency, workload, eventual consistency

• Features

• Cross datacenter, upgrades, indexes, persistence, tunability

• The vendor

• Viability, future direction, responsiveness, partnerships


Big Data – Petabyte range

Microsoft HDInsight

=

Hadoop as a service on Azure (+ .NET)


Hadoop components


Using Hadoop


Hadoop cluster size

Yahoo! wins with a massive 42000 node cluster


Questions

USE [Euricom]

SELECT [Question]

FROM [dbo].[FAQ]

WHERE [Answer] IS NULL

(0 row(s) affected)

Software

Sql vs nosql