INTRODUCTION TO DATABASES

ABSTRACT
Database management systems (DBMSs) are specially designed software
applications that interact with the user, other applications, and the database itself
to capture and analyze data.
RDBMS Vs NoSQL
NoSQL includes a wide range of different database technologies and were
developed as a result of surging volume of data stored. Relational databases are
not capable of coping with this huge volume and faces agility challenges. This is
where NoSQL databases have come in to play and are popular because of their
features. The session covers the following topics to help you choose the right
NoSQL databases.
EXISTING SYSTEM:
FLAT FILE SYSTEM
A list of names, addresses, and phone numbers written by hand on a sheet of
paper is a flat file database. This can also be done with any typewriter or word
processor. A spreadsheet or text editor program may be used to implement a flat
file database, which may then be printed or used online for improved search
capabilities.
DISADVANTAGES
1. Takes up a lot of disk space
2. very, very slow if you have to cross-reference anything
3. Limits you to one type of information per file


RDBMS
As the advancement flat file systems where replaced by relational databases.
Where data is structured data. But when it comes to Huge PetaBytes of data
RDMS loses it capability. Here comes NoSql Databases.
ADVANTAGES:
1. Reduces data Redundancy
2. Usually easier and faster to locate correct tables and Query Data
DISAVANTAGES:
1. Can handle only structured data.
2. Huge Data cannot be handled.
NoSQL
A NoSQL or Not Only SQL database provides a mechanism for storage and
retrieval of data that is modeled in means other than the tabular relations used in
relational databases. Motivations for this approach include simplicity of design,
horizontal scaling and finer control over availability. The data structure (e.g. key-
value, graph, or document) differs from the RDBMS, and therefore some
operations are faster in NoSQL and some in RDBMS. There are differences though,
and the particular suitability of a given NoSQL DB depends on the problem it must
solve
ADVANTAGES:
1. Can Handle Huge Data.
2. Its More Scalable
3. Its Cost-Effective and Open-Source


DISADVANTAGES:
1. Performance and Scaling > Consistency
2. It Has a Very Narrow Focus
3. It Doesnt Play Nice with Analytics

PROPOSED SYSTEM (HUGE AMOUNT OF DATA )
NoSQL databases are increasingly used in big data and real-time web applications.
NoSQL systems are also called "Not only SQL" to emphasize that they may also
support SQL-like query languages. Many NoSQL stores compromise consistency
(in the sense of the CAP theorem) in favor of availability and partition tolerance.
Barriers to the greater adoption of NoSQL stores include the use of low-level
query languages, the lack of standardized interfaces, and huge investments in
existing SQL. Most NoSQL stores lack true ACID transactions, although a few
recent systems, such as FairCom c-treeACE, Google Spanner and FoundationDB,
have made them central to their designs.
PROPOSED SYSTEM (CONSISTENCY):
One of the primary reasons that NoSQL will never wholly replace SQL is that it was
never meant to do so. NoSQL databases have a very narrow focus: they are
designed primarily for storage, and offer very little functionality beyond. When
transactions enter the equation, relational databases are still the better choice.
Further, NoSQL doesnt really do so well with data backup on its own.



J.SAGAR
11621A0524