NoSQL Database Concepts - PDF

Running head: DATABASE CONCEPTS
Database Concepts
(NoSQL)
Name of the student:
Name of the university:
Author Note

1DATABASE CONCEPTS
Discussion on Slide 2:
The presentation shows that it has been the alternative for conventional relational databases
where a date is placed in tabular format and the data-schema is designed carefully. This is done
before building the database. The databases are useful to work with huge volumes of distributed
data.
Discussion on Slide 3:
Here, the requirements and applications for scalability and performances that are outweighed
require rigid, immediate data consistency. This is provided by RDBMS towards applications of
transactional enterprises. However, NoSQL systems have never required following established
relational schema. Here large-scale web organizations like Amazon and Google use NoSQL
databases for focusing on various narrow operational goals. Then the relational databases are
employed as the adjuncts. Here high-grade consistency of data is needed.
Discussion on Slide 4:
The “key-value store: a model is simple. This leads towards developing key-value databases
that are highly active and largely scalable. This is for caching web applications and session
managements. Moreover, implementations have been a differing way they get oriented for working
with solid-state drives, disk-drives and RAM. Here, examples of this include Riak, Redis,
MemchacheDB, Berkeley DB and Aerospike.

2DATABASE CONCEPTS
Discussion on Slide 5:
It is seen that use of document schema has arisen because of use of JavaScript and JSON or
JavaScript Object Notation. This includes the format of data interchange and has gained wide
currency among different developers of web applications. However, XML and various other formats
can also be used here.
Discussion on Slide 6:
The evolution is seen under MarkLogic that has added graph stores and various other
elements to the original type of document database. Sometimes, the details of NoSQL gets mixed top
SQL elements generating multiple databases denoted as multi-model databases.
Discussion on Slide 7:
It has been making that more accessible to create significant different application changes
under real-time. This is done instead of worrying about various server interruptions. This indicates
that development is quicker. The developers have been needed to incorporate application-side code
for enforcing controls of data quality. This has been mandating the presence of particular fields, data
types and permissible values. Further, more sober NoSQL databases have allowed rule of validation
under the database. This has enabled users to enforce governance around data though maintaining
benefits of agility of dynamic schema.
Discussion on Slide 8:
Some of NoSQL databases have been offering completely manages integrated in-memory
database management layers for various workloads. It has been demanding highest throughputs and
least latencies (Rodrigues et al. 2018).

3DATABASE CONCEPTS
Discussion on Slide 9:
As the development cycle of implementing NoSQL has been quicker, the organizations have
been innovating more quickly and delivering superior customer experiences at lower costs.