Name Shivam Prasad

Reg No. 15BCE1196

1. Mondo DB
MongoDB is a cross-platform, document oriented database that provides, high
performance, high availability, and easy scalability. MongoDB works on concept
of collection and document

The following table shows the relationship of RDBMS terminology with

MongoDB.
RDBMS

MongoDB

Database

Database

Table

Collection

Tuple/Row

Document

column

Field

Table Join

Embedded Documents

Primary Key

Primary Key (Default key _id provided

by mongodb itself)

Database Server and Client

Mysqld/Oracle

mongod

mysql/sqlplus

mongo

Also for Key considerations for Determining if a NoSQL

DBMS meets your IT needs
MongoDB is a document database in which one collection holds different documents.
Number of fields, content and size of the document can differ from one document to
another.
Structure of a single object is clear.
No complex joins.
Deep query-ability. MongoDB supports dynamic queries on documents using a
document-based query language that's nearly as powerful as SQL.
Tuning.
Ease of scale-out MongoDB is easy to scale.
Conversion/mapping of application objects to database objects not needed.
Uses internal memory for storing the (windowed) working set, enabling faster access of
data.

Why Use MongoDB?

Document Oriented Storage
Data is stored in the form of JSON style documents.
Index on any attribute
Replication and high availability
Auto-sharding
Rich queries
Fast in-place updates
Professional support by MongoDB

Where to Use MongoDB? As we seit meets following it NEEDS!!!

Big Data

Content Management and Delivery

Mobile and Social Infrastructure
User Data Management
Data Hub

2. Cassandra
The data model of Cassandra is significantly different from what we normally
see in an RDBMS.

Cluster
Cassandra database is distributed over several machines that operate
together. The outermost container is known as the Cluster. For failure
handling, every node contains a replica, and in case of a failure, the replica
takes charge. Cassandra arranges the nodes in a cluster, in a ring format,
and assigns data to them.

Keyspace
Keyspace is the outermost container for data in Cassandra. The basic
attributes of a Keyspace in Cassandra are

Replication factor It is the number of machines in the cluster that will

receive copies of the same data.

Replica placement strategy It is nothing but the strategy to place replicas

in

the

ring.

strategy), old

We

have

network

strategies

such

topology

as simple

strategy (rack-aware

strategy (rack-aware

strategy),

and network topology strategy (datacenter-shared strategy).

Column families Keyspace is a container for a list of one or more column

families. A column family, in turn, is a container of a collection of rows. Each row
contains ordered columns. Column families represent the structure of your data.
Each keyspace has at least one and often many column families.

A Cassandra column family has the following attributes

keys_cached It represents the number of locations to keep cached per

SSTable.

rows_cached It represents the number of rows whose entire contents will be

cached in memory.

preload_row_cache It specifies whether you want to pre-populate the row

cache.

Note Unlike relational tables where a column familys schema is not

fixed, Cassandra does not force individual rows to have all the columns.
The following figure shows an example of a Cassandra column family.

Following key considerations for Determining if a NoSQL DBMS meets

our IT needs:Cassandra has become so popular because of its outstanding technical
features. Given below are some of the features of Cassandra:

Elastic scalability - Cassandra is highly scalable; it allows to add more

hardware to accommodate more customers and more data as per requirement.

Always on architecture - Cassandra has no single point of failure and it is

continuously available for business-critical applications that cannot afford a
failure.

Fast linear-scale performance - Cassandra is linearly scalable, i.e., it

increases your throughput as you increase the number of nodes in the cluster.
Therefore it maintains a quick response time.

Flexible data storage - Cassandra accommodates all possible data formats

including: structured, semi-structured, and unstructured. It can dynamically
accommodate changes to your data structures according to your need.

Easy data distribution - Cassandra provides the flexibility to distribute data

where you need by replicating data across multiple data centers.

Transaction

support -

Cassandra

supports

properties

like

Atomicity,

Consistency, Isolation, and Durability (ACID).

Fast writes - Cassandra was designed to run on cheap commodity hardware. It

performs blazingly fast writes and can store hundreds of terabytes of data,
without sacrificing the read efficiency.

3. CouchDB

CouchDB is an open source database developed by Apache software

foundation. The focus is on the ease of use, embracing the web. It is a
NoSQL document store database.
It uses JSON, to store data (documents), java script as its query
language to transform the documents, http protocol for api to access
the documents, query the indices with the web browser. It is a multi
master application released in 2005 and it became an apache project
in 2008.

Key consideration for why couchdb should be determining if it meets

needs of IT INDUSTRY

CouchDB have an HTTP-based REST API, which helps to communicate

with the database easily. And the simple structure of HTTP resources
and methods (GET, PUT, DELETE) are easy to understand and use.
As we store data in the flexible document-based structure, there is no
need to worry about the structure of the data.
Users are provided with powerful data mapping, which allows querying,
combining, and filtering the information.
CouchDB provides easy-to-use replication, using which you can copy,
share, and synchronize the data between databases and machines.

Features of CouchDB
Document Storage
CouchDB is a document storage NoSQL database. Documents are the
primary unit of data, each field is uniquely named and contain values of
various data types such as text, number, Boolean, lists, etc... In these
documents there is no set limit to text size or element count.
CouchDB provides an API called RESTful HTTP API for reading and updating
(add, edit, delete) database documents.
Below given is the sample JSON document structure followed by couchDB..

{
"field" : "value",
"field" : "value",
"field" : "value",
}

ACID Properties
The CouchDB file layout and commitment system features all the ACID
properties.
Once the data is entered in to the disc it will not be overwritten. Document
updates (add, edit, delete) follow Atomicity, i.e., they will be saved
completely or not saved at all. The database will not have any partially
saved or edited documents.
Almost all of these update are serialized and any number of clients can read
a document without waiting and without being interrupted.

Compaction
Compaction is an operation to avail extra disc space for the database by
removing unused data. While performing compaction operation on a
particular file, a file with the extension .compaction is created and all the
active/actual data is copied (cloned) to that file, when the copying process
is finished then the old file is discarded. The database remains online during
the compaction and all updates and reads are allowed to complete
successfully.

Views
Data in CouchDB is stored in semi-structured documents that are flexible
with individual implicit structures, but it is a simple document model for
data storage and sharing. If we want see our data in many different ways,
we need a way to filter, organize and report on data that hasnt been
decomposed into tables.

To solve this problem, CouchDB provides a view model. Views are the
method of aggregating and reporting on the documents in a database, and
are built on-demand to aggregate, join and report on database documents.
Because views are built dynamically and dont affect the underlying
document, you can have as many different view representations of the
same data as you like.