Moving Beyond RDBMSs

There are alternative examples, such as document and graph databases

colloquially known as NoSQL databases that have their own advantages and
disadvantages.
Yet RDBMSs arent perfect. When the data gets big, they dont generally scale
easily even with sharding (when the data is not static as everyday there is new
types of changes happening to data throughout time). Changes to a single
column reverberate among views, stored procedures and application code. That
is why we have other solutions if RDBMS solutions are not good enough.
Document databases
Document databases like MongoDB and Apache CouchDB both open source is
the first solution we discuss. Documents are flexible binary JSON ( (JavaScript
Object Notation) is a lightweight data-interchange format. It is easy for humans
to read and write.) structures where child records modeled with relationships in a
RDBMS are instead embedded within the documents which make it easy to make
conclusions.
Scalability and simplicity is a big advantage of this database. Once one becomes
familiar with JSON, querying for results is straightforward. Without a predefined
schema (a representation of a plan), data can evolve as needed. Joins (a clause
combines columns from one or more tables in a relational database) are removed
because data is denormalized (the process of attempting to optimize the read
performance of a database by adding redundant data or by grouping data.) And
because JSON is the most common data format on the Web, developers may be
able to use a driver to pass data from the database straight through to the front
end to understand.

Graph databases
With a graph database, imagine a bulletin board used by the Major Crimes Unit
to display an evolving chart for criminal organizations. Data is modeled as a
collection of nodes( a visual representation of an entity in a diagram.) connected
by edges as well both endowed with attributes. As always, the data model
must be optimized for the anticipated queries for example, when deciding
whether certain data belongs in a node or edge (An Edge is a visual
representation of a relation.).
This is a fundamental shift from RDBMSs. When working with network data (such
as SIGINT, financial transactions, or migration patterns) modeling in tables and
relationships can be awkward. Much worse, RDBMSs can be quite slow for the
kinds of queries that matter on graphs like shortest paths, community detection
and centrality.

RDBMS

Graphical