Overview
NoSQL is generally interpreted as “Not only SQL” [1]. It is a class of database management systems that are used for non-relational database. Typically NoSQL database does not use two-dimensional table to store data. The four generally categories of NoSQL database are key-values database, column databases, document databases, and graph databases [2]. NoSQL database is an indispensable part of big data. Most company choose NoSQL database because it yields better performance when compared to relation database. Many relational databases have been existing for more than 20 years, while most NoSQL databases have a history of less than 5 years. Because NoSQL databases are so young, they exposes lots of security issues. Many NoSQL databases are still focusing on adding features and improving performance, while strength security mechanism is still a low priority task. There were already two data breaches happened in companies that are using NoSQL databases (MongoHQ in 2013 and LinkedIn in 2012 [3]).
Detailed result
NoSQL database characteristics
The problem of relational database is that its performance degrade significantly while handling exponential growth of semi-structured data or unstructured data [4]. The NoSQL databases possess properties called BASE (Basically available, Soft state, and eventually consistent) that makes it much more scalable than relational databases. As the CAP theorem [5] said, a database system cannot have high consistency, high availability,
In order to overcome these limitations, a new database model known as Not Only SQL (NoSQL) database emerged with a set of new features. The main objective of NoSQL is not to discard SQL, but to be used as an alternative database data model for new features [1] [2] [3]. NoSQL database increases the performance of relational databases by a set of new characteristics and advantages. In contrast to relational databases, NoSQL databases introduced an additional feature that provides flexible and horizontal scalability and taking advantage of new clusters. The rise of NoSQL provides cost-effective management of data in modern web applications. With its new features, NoSQL can be used with applications that have a large transaction, and require low-latency access to huge datasets, service availability while
Provide reasoning to support the use of the NoSQL database as the database of choice to solve the problem faced by TWC. Identify one strength and one weakness for each of the other three kinds of databases to solve the problem for TWC.
For the purpose of this paper, we are going to focus on these three type of NoSQL database BigTable, Cassandra, DynamoDB.
Tracking the concept of Big Data management from Relational Databases Management Systems to the current NoSQL database, this paper surveys the Big Data challenges from the perspective of its characteristics Volume, Variety and Velocity, and attempts to study how each of these challenges are addressed by various NoSQL systems. NoSQL is not a single system that can solve every single Big Data problem; it is an eco-system of technologies where different type of NoSQL databases are optimized to address various types of big data challenges by providing schema-less modeling and automatic
Over many ago relational databases reside most of the data but after the introduction of NoSQL database had changed this procedure. Most of the unstructured data had been sent to NoSQL database. Relational database systems, which showed good performance before the birth of internet and cloud computing era is now unable to control the heat of new technologies. To stabilize this situation new requirements were set to design by RDBMS. To meet these challenges they need highly scalable and unstructured data model with high performance; so they choose NoSQL database (Muhammad Mughees, 2013).
Column-based or wide column NOSQL systems: These systems segment a table by column into column families where every column family is put away in its own records. They additionally permit forming of data qualities. Chart based NOSQL systems: Data is spoken to as graphs, and related hubs can be found by navigating the edges utilizing way expressions Data with the accompanying attributes is appropriate for a NoSQL system firstly, Data volume becoming quickly secondly, Columnar development of data then, Document and tuple data Lastly, Hierarchical and graph data. Data with the accompanying qualities may be more qualified for a conventional relational database management system is On-Line Transaction Processing required atomicity, consistency, disengagement, toughness prerequisites (ACID) then Complex data relationship and Complex question prerequisites [2] Apache Cassandra are example of BigTable-style Databases Oracle Coherence, Kyoto Cabinet is case of of Key-Value Stores. mongo DB and Couch DB is example of document database and neo4j and flock dB is case of graph database. [4]. I have selected document base data modeling to compare and contras with relational data modeling.
STRUCTURE OF DATA: The data structure of a relational database comprises of table structure. Every table is identified by a unique name or label. The data tables are described as the collection of rows and columns. Each row of the table is known as the record and each column is known as the field of the specific data table. All the data sets are well organized and logical linked to each other through definite and unique relationships. A table, therefore can also be defined as the “structured collection of relationships”. The fundamental aim of developing No SQL database systems is to easily and effectively handle vast quantity of data or information in advanced web-scale applications. In order to achieve this purpose, the No SQL systems are designed as the schema-free database systems. There are different modes to define the No SQL databases that typically depend on the requirements of the data that has to be managed. The main No SQL data structures include column database, key-value store database, document store database, graph database and
NoSQL databases are a significant departure from the relational model that has dominated the business world for the past few decades. Standing for “Not Only SQL,” these products are all some variation of a non-relational, key-value pair database, and they are becoming very popular with companies that use Big Data and prioritize speed or availability over consistency of data.
“NoSQL practitioners focus on physical data model design rather than the traditional conceptual / logical data model process” (Hsieh, 2014). The mindset of the data modelers have changed in recent years. The flexibility, scalability and the ability to handle variety of structured to unstructured data of the NoSQL data bases have made the data modelers to think more in business –centric notion.
A No-SQL (often interpreted as Not Only SQL) database provides a mechanism for storage and retrieval of data that is modelled 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 modern RDBMS advancements are not capable of supporting unstructured information with ideal space necessity. The plan winds up plainly mind-boggling and is henceforth troublesome for designers. The requirement for unstructured information administration is so annoying with conventional RDBMS arrangements (Big data in financial services industry: Market trends, challenges, and prospects 2013 - 2018). Moreover, RDBMS turns out to be an exorbitant answer for creating light-footed web applications with direct information investigation necessities. NoSQL is developing as a proficient possibility in this situation, which connects the issues related with RDBMS innovation. The market development can credit to creative dispatches of NoSQL arrangements, and collective endeavors by NoSQL sellers and clients. The endeavors of organizations, to enhance their market offerings, are creating the request of NoSQL, as a back-end bolster (Big data in financial services industry: Market trends, challenges, and prospects 2013 - 2018). The emergence of agile software development is creating the demand for NoSQL (Big data in financial services industry: Market trends, challenges, and prospects 2013 - 2018). They offer users much more avenues to accept data in many different forms. NoSQL is adaptable as SQL but offers many more uses that can apply to many organizations.
With its dispatch in 2015 the AWB uses devices like Kinesis, which is for continuous spouting, S3 which is for basic accumulating stage and DynamoDB – it is immense limit with respect to NoSQL database.
This paper will outline and describe three vendors that provide the Hadoop NoSQL database program to enterprises. Each of these companies see themselves as uniquely different, thus positioning themselves within a market place that has begun to become highly competitive in the “Big Data” age. I will provide an outline of the talking points that will be discussed for each company, starting with a brief description of the Hadoop NoSQL open-source database program, then I will discuss each company on the evaluation categories, and conclude with options for whether to move forward with either of these vendors. After the conclusion the reader will have the information on these vendors and the confidence to be able to decide on which choice would be best for the business.
Abstract- The multidimensional growth in computing systems and technologies have resulted in advanced scalable, portable and large scale integrated systems and technologies. Datacenters, virtualization, cloud and WEB2 technologies are the frontiers of such growth. [1] Cloud computing represents an important step towards realizing McCarthy’s dream that all aspects of computation may someday be organized as a public utility service. Both public and private cloud platforms are looking to deliver the benefits of cloud computing to their customers. The database is a critical part of this platform. Therefore cloud database need to be compatible with cloud computing. [5] Though cloud computing offers huge opportunities to the IT industry, there are many issues still to be addressed in the current scenario.[6]
NoSQL was created in the response to relational databases not being able to handle the scale and changing challenges of modern applications, they also cannot take advantage of the cheap, easy storage abilities and also the processing power accessible now. NoSQL includes a variety of different technologies that were developed in response to the surge of data stored by users, objects and products. They were also developed to contend with the rising frequency that the data is accessed and the performance and processing needs. [7]