Difference between Nosql and SQL

1. Overview

When it comes to choosing a database the biggest decisions are picking a relational (SQL) or non-relational (NoSql) data structure. While both the databases are viable options still there are certain  key differences between the two that users must keep in mind when making a decision

2. NoSQL

2.1 What is NoSQL

NoSQL databases are purpose-built for specific data models and have flexible schemas for building modern applications. NoSQL databases are widely recognized for their ease of development, functionality, and performance at scale. These types of databases are optimized specifically for applications that require large data volume, low latency, and flexible data models, which are achieved by relaxing some of the data consistency restrictions of other databases.

2.2 How Does a NoSQL work

In a NoSQL database, a book record is usually stored as a JSON document. For each book, the item, ISBN, Book Title, Edition Number, Author Name, and AuthorID are stored as attributes in a single document. In this model, data is optimized for intuitive development and horizontal scalability.

2.3 Why should you use a NoSQL

• Flexibility
• Scalability
• High-performance
• Highly functional

3. Comparison between NoSQL and SQL

Features	SQL	NoSQL
Architecture	Relational Database Management System(RDBMS)	Non-relational or distributed Database System
Schema Type	Fixed or Static or Predefined Shema	Dynamic schema
Query Language	Structured Query Language (SQL)	No Declarative Query Language
Hierarchical Data	Not suited	Best suited
Complex Query	Best suited	Not so good
Scalable Type	Vertically Scalable	Horizontally Scalable
Productions	MySQL, Oracle, Postgres, etc.	MongoDB, Apache CouchDB
Pros	Easy to use and setup Universal, compatible with many tools Good at high-performance workloads Good at structure data Protest the integrity of the database by providing ACID compliance	No investment to design model Rapid development cycles In general faster than SQL Runs well on the cloud Easily scale by spreading around multiple servers
Cons	Time-consuming to understand and design the structure of the database Can be difficult to scale	Unsuited for interconnected data Technology still maturing Can have a slower response time
when to use	The preferable option for structure and schemas	Developing an application within a speculated time

3. References

https://aws.amazon.com/nosql/

https://www.geeksforgeeks.org/difference-between-sql-and-nosql/

https://www.agiratech.com/the-key-differences-between-sql-and-nosql-database/

https://www.thegeekstuff.com/2014/01/sql-vs-nosql-db

https://www.guru99.com/sql-vs-nosql.html

https://www.geeksforgeeks.org/sql-vs-nosql-which-one-is-better-to-use/