NoSQL - Revision history

User at 20:15, 3 December 2021

2021-12-03T20:15:08Z

User at 18:09, 3 December 2021

2021-12-03T18:09:47Z

User at 18:00, 3 December 2021

2021-12-03T18:00:35Z

User: Created page with "A '''NoSQL''' (originally referring to "non-SQL" or "non-relational") database provides a mechanism for storage and retrieval of data that is modeled in means other than the t..."

2021-12-03T17:50:46Z

Created page with "A '''NoSQL''' (originally referring to "non-SQL" or "non-relational") database provides a mechanism for storage and retrieval of data that is modeled in means other than the t..."

New page

A '''NoSQL''' (originally referring to "non-SQL" or "non-relational") database provides a mechanism for storage and retrieval of data that is modeled in means other than the tabular relations used in relational databases. Such databases have existed since the late 1960s, but the name "NoSQL" was only coined in the early 21st century, triggered by the needs of Web 2.0 companies. NoSQL databases are increasingly used in big data and real-time web applications. NoSQL systems are also sometimes called "Not only SQL" to emphasize that they may support SQL-like query languages or sit alongside SQL databases in polyglot-persistent architectures. The term NoSQL was used by Carlo Strozzi in 1998 to name his lightweight Strozzi NoSQL open-source relational database that did not expose the standard Structured Query Language (SQL) interface, but was still relational.<ref>Definition - What Does NoSQL Mean? [https://en.wikipedia.org/wiki/NoSQL Wikipedia]</ref>

== History of NoSQL Databases<ref>Brief history of NoSQL databases [https://www.mongodb.com/nosql-explained MongoDB]</ref> ==
NoSQL databases emerged in the late 2000s as the cost of storage dramatically decreased. Gone were the days of needing to create a complex, difficult-to-manage data model in order to avoid data duplication. Developers (rather than storage) were becoming the primary cost of software development, so NoSQL databases optimized for developer productivity.

[[File:NoSqL History.png|400px|History of NoSqL]]

As storage costs rapidly decreased, the amount of data that applications needed to store and query increased. This data came in all shapes and sizes — structured, semi-structured, and polymorphic — and defining the schema in advance became nearly impossible. NoSQL databases allow developers to store huge amounts of unstructured data, giving them a lot of flexibility.

Additionally, the Agile Manifesto was rising in popularity, and software engineers were rethinking the way they developed software. They were recognizing the need to rapidly adapt to changing requirements. They needed the ability to iterate quickly and make changes throughout their software stack — all the way down to the database. NoSQL databases gave them this flexibility.

Cloud computing also rose in popularity, and developers began using public clouds to host their applications and data. They wanted the ability to distribute data across multiple servers and regions to make their applications resilient, to scale out instead of scale up, and to intelligently geo-place their data. Some NoSQL databases like MongoDB provide these capabilities.

== Types of NoSQL<ref>Types of data models with NoSQL databases [https://azure.microsoft.com/en-us/overview/nosql-database/ Microsoft]</ref> ==
Most nonrelational, high-performance databases, sometimes called “not only SQL,” can also handle highly structured data—they just aren’t limited to fixed data models like relational (SQL) databases. The four most common types of NoSQL databases are:
*Key-value: Key-value stores pair keys and values using a hash table. Key-value types are best when a key is known and the associated value for the key is unknown.
*Document: Document databases extend the concept of the key-value database by organizing entire documents into groups called collections. They support nested key-value pairs and allow queries on any attribute within a document.
*Columnar: Columnar, wide-column, or column-family databases efficiently store data and query across rows of sparse data and are advantageous when querying across specific columns in the database.
*Graph: Graph databases use a model based on nodes and edges to represent interconnected data—such as relationships between people in a social network—and offer simplified storage and navigation through complex relationships.

== NoSQL vs SQL Databases
Modern application developers have many choices when faced with deciding when and how to persist a piece of data. While SQL databases are great at solving traditional application problems like data normalization, strictly consistent data, and complex queries to access that data, NoSQL databases turn out to be great at processing unstructured data dynamically.

[[File:SQL Vs NoSQL.png|400px|SQL Vs. NoSQL]]

1) NoSQL is not a replacement for RDBMS. 
2) SQL databases are relational, NoSQL databases are non-relational. 
3) SQL databases use structured query language and have a predefined schema. NoSQL databases have dynamic schemas for unstructured data. 
4) SQL databases are better for multi-row transactions, NoSQL is better for unstructured data like documents or JSON. 
5) Most SQL databases require you to scale-up vertically, NoSQL databases allow you to scale-out horizontally. 
6) Queries in NoSQL databases can be faster than SQL databases. 

== Why Use SQL<ref>Why should you use a NoSQL database? [https://aws.amazon.com/nosql/ AWS]</ref>
NoSQL databases are a great fit for many modern applications such as mobile, web, and gaming that require flexible, scalable, high-performance, and highly functional databases to provide great user experiences.
*Flexibility: NoSQL databases generally provide flexible schemas that enable faster and more iterative development. The flexible data model makes NoSQL databases ideal for semi-structured and unstructured data.
*Scalability: NoSQL databases are generally designed to scale out by using distributed clusters of hardware instead of scaling up by adding expensive and robust servers. Some cloud providers handle these operations behind-the-scenes as a fully managed service.
*High-performance: NoSQL database are optimized for specific data models and access patterns that enable higher performance than trying to accomplish similar functionality with relational databases.
*Highly functional: NoSQL databases provide highly functional APIs and data types that are purpose built for each of their respective data models.

@@ Line 1: / Line 1: @@
-A '''NoSQL''' (originally referring to "non-SQL" or "non-relational") database provides a mechanism for storage and retrieval of data that is modeled in means other than the tabular relations used in relational databases. Such databases have existed since the late 1960s, but the name "NoSQL" was only coined in the early 21st century, triggered by the needs of Web 2.0 companies. NoSQL databases are increasingly used in big data and real-time web applications. NoSQL systems are also sometimes called "Not only SQL" to emphasize that they may support SQL-like query languages or sit alongside SQL databases in polyglot-persistent architectures. The term NoSQL was used by Carlo Strozzi in 1998 to name his lightweight Strozzi NoSQL open-source relational database that did not expose the standard Structured Query Language (SQL) interface, but was still relational.<ref>Definition - What Does NoSQL Mean? [https://en.wikipedia.org/wiki/NoSQL Wikipedia]</ref>
+== What is NoSQL<ref>Definition - What Does NoSQL Mean? [https://en.wikipedia.org/wiki/NoSQL Wikipedia]</ref> ==
@@ Line 39: / Line 43: @@
-== Why Use SQL<ref>Why should you use a NoSQL database? [https://aws.amazon.com/nosql/ AWS]</ref>
+== Why Use SQL<ref>Why should you use a NoSQL database? [https://aws.amazon.com/nosql/ AWS]</ref> ==
 NoSQL databases are a great fit for many modern applications such as mobile, web, and gaming that require flexible, scalable, high-performance, and highly functional databases to provide great user experiences.
 *Flexibility: NoSQL databases generally provide flexible schemas that enable faster and more iterative development. The flexible data model makes NoSQL databases ideal for semi-structured and unstructured data.
@@ Line 47: / Line 51: @@
-== Trends and their Technical Challenges that NoSQL Addresses<ref>Five trends creating new technical challenges that NoSQL DBs address
+== Trends and their Technical Challenges that NoSQL Addresses<ref>Five trends creating new technical challenges that NoSQL DBs address [https://www.couchbase.com/resources/why-nosql Couchbase]</ref> ==
 These companies and hundreds more like them are turning to NoSQL because of five trends that present technical challenges that are too difficult for most relational databases.
@@ Line 84: / Line 88: @@
 *Supporting multiple mobile platforms with a single backend
 |}

@@ Line 51: / Line 51: @@
 {| class="wikitable"
-! style="color:red" | Digital Economy trends
+! style="color:red";  | '''Digital Economy Trends'''
-! style="color:red" | Requirements
+! style="color:red"; | '''Requirements'''
 |-
 |1. More customers are going online

@@ Line 24: / Line 24: @@
-== NoSQL vs SQL Databases
+== NoSQL vs SQL Databases<ref>NoSQL vs SQL Databases [https://k21academy.com/dba-to-cloud-dba/nosql-database-service-in-oracle-cloud/ K21 Academy]</ref> ==
 Modern application developers have many choices when faced with deciding when and how to persist a piece of data. While SQL databases are great at solving traditional application problems like data normalization, strictly consistent data, and complex queries to access that data, NoSQL databases turn out to be great at processing unstructured data dynamically.
@@ Line 45: / Line 45: @@
 *High-performance: NoSQL database are optimized for specific data models and access patterns that enable higher performance than trying to accomplish similar functionality with relational databases.
 *Highly functional: NoSQL databases provide highly functional APIs and data types that are purpose built for each of their respective data models.