Home
Business Guide
 
simplicable technology guide   »  big data   »  nosql vs sql

NoSQL Versus SQL: 7 Critical Differences

        posted by , December 16, 2012

NoSQL databases were developed by companies such as Google, Yahoo and Facebook as a means for dealing with massive quanities of data.

As the name suggests, NoSQL databases don't use standard query language (SQL). They also have profoundly different performance characteristics and architectures from traditional relational databases (SQL databases).

The key differences to remember are:

1. NoSQL is about big data (mostly)

NoSQL tools evolved as a means of managing large volumes of data. In other words, they scale horizontally.


2. NoSQL databases are less structured

Data in a NOSQL database doesn't necessarily follow a fixed schema. It's ideal for processing mixed sets of structured and unstructured data.


3. NoSQL doesn't maintain complex relationships between data

NoSQL is about accessing large amounts of data with simple data structures such as collections of key/value pairs. Complex relationships between data aren't typically maintained.


4. NoSQL doesn't give many guarantees

Relational databases guarantee atomicity, consistency, isolation and durability (ACID) of transactions. NoSQL makes no such guarantees.

In many cases, NoSQL databases may only guarantee that data will eventually be consistent if there's enough time and processing power.


5. NoSQL is distributed and fault-tolerant

NoSQL is typically a distributed processing technology (e.g. deployed to cloud). Data may be replicated many times across the architecture with no single point of failure.


6. NoSQL lacks the run-time power of SQL

SQL is far more flexible for runtime operations. It can leverage relationships between data to execute complex queries.


7. NoSQL and SQL Databases Are Often Used Together

NoSQL and SQL databases solve different problems.

NoSQL can process large amounts of structured and unstructured data. SQL can represent complex relationships between data and process complex queries.

It's common for a single solution to leverage both NoSQL and SQL technologies.


3 Shares Google Twitter Facebook



Related Articles



Enterprise Architecture
How to architect an organization.




Enterprise Architecture (EA) is supposed to help manage IT risks — but is it possible that EA itself introduces new risks?

Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats. ~ Howard Aiken

Why risks and even vulnerabilities aren't necessarily bad.

Take a few minutes to learn about the Zachman Framework — a framework for Enterprise Architecture.


Recently on Simplicable


9 Reasons You Need a Current State Architectural Blueprint

posted by Anna Mar
A current state enterprise architecture blueprint represents your organization's high level architecture. It's probably the most important documentation that any IT organization can create and maintain.

The 5 Levels of Enterprise Integration

posted by Anna Mar
Enterprise Integration has traditionally focused on moving data from one database to another. Recent technology trends have challenged this approach.

Do "Real" Architects Dislike Technology Architecture?

posted by Anna Mar
Go to any job site and query architect — you'll be hard pressed to find the adverts for construction architects in the sea of job postings for technology architects.

101 Game Design Principles for Social Media

posted by Anna Mar
The convergence of social media, software and gaming.

Sitemap













about     contact     sitemap     privacy     terms of service     copyright