Case Study
Q1: Compare between Relational database and NoSQL database.
Answer: Compare between Relational database and NoSQL database.
Relational Databases
Relational databases (RDBMS) have
History of Relational been around for over 40 years.
Databases (RDBMS) Historically, they’ve worked well,
for the times when data structures
and NoSQL were much more simple and static.
However, as technology and big data
applications advanced, the traditional
SQL-based relational database was
less equipped to handle rapidly
expanding data volumes and the
growing complexities of data
structures.
In a relational database, you are
Data Models and required to define your schema
Schema before adding data to the database.
Relational databases are table-based.
Data Structure Relational databases were built
during a time that data was mostly
structured and clearly defined by
their relationships.
Relational databases are vertically
Scaling scalable but typically expensive.
Since they require a single server to
host the entire database, in order to
scale, you need to buy a bigger, more
expensive server.
NoSQL
In the last decade, the non-relational,
NoSQL databases became more
popular for offering a more flexible,
scalable, cost-efficient, alternative to
the traditional SQL-based relational
databases.
NoSQL databases feature dynamic
schema, and allow you to use what’s
known as “unstructured data.” This
means you can build your
application without having to first
define the schema.
NoSQL databases can be document
based, graph databases, key-value
pairs, or wide-column stores.
Scaling a NoSQL database is much
cheaper, compared to a relational
database, because you can add
capacity by scaling horizontally over
cheap, commodity servers.
 Relational databases are typically NoSQL databases tend to be more a
Development Model closed source with licensing fees part of the open-source community.
baked into the use of their software.