Essays /

Nosql Database Essay

Essay preview

Trends in Database & NoSQL

This paper discusses about the trends in databases and new evolving field of non-relational databases. Non-relational databases are evolving these days due to its various advantages over relational databases. Non-relational databases consists of various types of databases which are used to handle different types of data and have different features like Key value stores, document oriented databases and column oriented databases, graph databases and many others. Non-relational databases are very popular and in use these days because of their various advantages over the relational databases. The non-relational database handles various types of data like graph, object, semi structured and structure data. These databases can handle large amount of data and provide scalability. Due to which these are very useful to use in distributed environment like in cloud computing applications. The major players who are leading the trends of the ever evolving databases are Amazon, Google and Microsoft. These three giants have the major share of the market. In today’s world where the data, information and its storage has become important than ever, different industry sectors are utilizing the technology. Health industries have started using the databases extensively and the technology has been at the epitome of its use. Patients records, different instruments required in the hospital, appointment dates are some small examples where databases are used to store information in this vast industry and there is a huge scope as the health industry is highly replying on the growth of IT and database involvement. KEYWORDS

Database, NoSQL, NewSQL, RDBMS, Comparison, Advantages, Disadvantages

1. Introduction
In today’s highly competitive and customer driven environment depends on the company’s ability to understand and respond to the customer needs. Right data collection is a priority and it is very essential. Transaction-intensive, customer-facing applications, as well as high-volume CRM and ERP applications, are collecting and storing more data, is not abiding the Moore’s law, instead it growing at a much faster rate as suggested by Moore. As these applications rely on complex relational databases, managing continuous database growth is absolutely necessary for controlling costs, improving customer satisfaction and enhancing decision support to ensure long-term success. The rapid growth of the Internet and eBusineses, the increase in online transaction processing and the expansion of large databases that support customer-facing applications have contributed significantly to the data explosion. This growth is driving increasing demand for data storage and data management solutions. There is an increasing need to maintain easy access to historical information for business or regulatory requirements. For example, a company may need to protect its interests by retrieving historical financial transactions to satisfy customer inquiries and resolve claims. In other cases, corporate policy or government regulations dictate that data must remain accessible for years after it is collected. For many organizations, accelerating data growth and the need to store historical information are putting a real strain on enterprise IT system capacity. As a result, data storage is quickly becoming the biggest expense in enterprise IT budgets, responsible for up to 30 percent of capital expenditures, despite the fact that the cost of traditional disk storage is dropping.

2. Background
2.1 Relational Database
E.F Codd invented the relational database in 1970. A relational database is a collection of data items organized in formally-described tables from which data can be accessed or reassembled in many different ways. Mostly all the relational databases use Structured Query Language (SQL) to access and modify the data stored in the database. Originally it was based upon relational calculus and relational algebra and is subdivided into elements such as clauses, predicates, queries and statements. Some of the benefits of the database designed according to the relational model are: Most of the information is stored in the database and not in the application, so the database is self-documenting. It is easy to add, update or delete data.

It gives benefits of data summarization, retrieval and reporting. 2.2. Tools of Relational Database
The two most extensively used relational databases are MySQL and Oracle. MySQL is more popular with the websites. It is a light weight system which is extremely fast but Oracle is majorly used in case of large database requirement like Banking, Insurance, ERP and finance companies. It is used to solve complex problems and supports large OLTP environments. Though they majorly wor...

Read more


-0 -25 -28 -319 -355 -4 -4401 -7695 -9162 /10 /design.phptem /roedunet.2011.5993686 /wiki/mongodb/ 0 0975 1 10 10.1109 10gen 10th 11 12 13 1958 1970 2 2.1 2.2 2.3 2008 2010 2011 2012 23 26 26.00 27 3 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.4 3.4.1 3.4.10 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.4.7 3.4.8 3.4.9 3.5 3.5.1 3.5.2 3.5.3 3.6 30 314 351 39 4 4000 48 5 6 6th 7 8 888 8887 9 978 a.b abid abil abolish absolut abstract acceler accept access accesses/updated accord achiev acid acm across actual ad add adjac adopt advantag affect afford aggreg agil ago al algebra allow almost along also alter although amazon among amount analyt andrew anoth answer api app app-develop appli applic appoint approach appropri aravindh arb arbor architectur aris around array aspect associ assum asynchron author automat avail avoid awar b.g backend background bank base basi basic becom behavior behind belong benefit best better beyond bhat big bigger biggest bigtabl blend breakdown broad bson bucur budget burrow busi c cach calcul calculus cannot capac capit care case categori cattel certain chandra chang characterist cheaper choos chosen chunk claim clarenc class classic classif claus client clock clockwis cloud cluster clutter codd collect column column-ori columnar combin comment common communic communiti compani compar comparison competit complex compon compress comput concept conclud conclus concurr confer confus connect consid consider consist consum contain content continu contribut control convent converg coordin corpor cost could crm cross cross-serv current custom customer-fac data databas dataset date day dbms dean deborah decemb decis defin delet demand depend deriv describ design despit detail determin develop dictat differ dimens dimension direct disadvantag discuss disk distribut divid document document-ori doesn doi done down drawback drill drill-down drive driven drop du due dynam e e.f e.g earlier easi easier easili ebusines edg effici elast element elimin employ enabl encapsul enclos encod engin enhanc ensur enter enterpris entiti environ epitom equival erp especi essbas essenti et even eventu ever everi evolv exampl execut exist expand expans expenditur expens explain exploit explos express extens extra extrem face facebook fact famili fashion fast faster fastest fay featur field fike fill final financ financi find fix flash flexibl focus follow form formal formally-describ format found four full fulli fully-funct function fundament general generat geograph get ghemawat giant give given good googl govern graph great grid grow growth gruber guan guarante h haihong han hand handl hardwar hash health henc heterogen hewlett high high-perform high-volum higher histor hole horizont hospit howev hp hsieh huge hurt hybrid i.e ibm ici icpca icpca.2011.6106531 idea ieee ieee/acis imagin implement import improv in-memori includ increas industri inform inherit inquiri instanc instead instrument insur integ integr intellig intens interact interconnect interest intermedi intern internet interpret introduct invent involv iri isbn item j jadhav java jay jerey jian jing join journal json jund june key key-valu keyword known krep languag larg last latest law layer le lead leav leavitt less level licens light like limit linkedin list live load local logic long long-term look loos loosen loss lot low luhn m made main maintain major make manag mani manual map map-reduc mark market massiv matrix maximum may mean meaning measur mechan meina memori mention merg method microsoft microstrategi mike mix model modern modif modifi mongodb moor most move mpp much multi multi-nod multi-vers multidimension multimodel multipl multiprocess multivalu multivers must mvcc mysql n n-dimension name nativ natur neal necessari need neither network new newer newsql no.20 node non non-rel nosql note novel nowaday number object obsolet obtain obvious occur oct offer offic often old oltp one onlin onto oodbm open oper optim option oracl order ordin organ orient origin other overal overhead overtak overwrit p packard page pair paper parallel part particular partit path patient pattern pdf peopl percent perform period pertin pervas pick piec place plan platform player point polici popular pose possibl post pp.1-5 pp.363-366 practic precompil predic primari primit prioriti privat problem problemat proceed process produc product program project promis properti protect protocol provid purpos put quantiti quarter queri question quick ram rang rapid rate rather rdbms read readi real real-tim reason reassembl rebuild recent record redbrick redesign redistribut reduc refer regul regular regulatori relat releas relev reli remain remot remov replac repli replic replica report repres requir research resid resolv resourc respond respons restrict result retriev reusabl rick right ring rise robert roedunet roll roll-up row run russom sanjay satisfact satisfi scalabl scale scenario schema schema-less scienc scope section sector self self-contain self-docu semi sens serial server set sever shard share shared-memori sharing-key shift shortcom shraddha shreeharsha shut side sigmod signific similar simpl simpler simpli simplic simplifi sinc singl single-shar single-shard-key small smaller society0018 solut solv someon sometim song sourc space specif specifi specifi speed sponsor sql stake standard start state statement still storag store strain string structur studi sub subdivid submit success suffer suggest summar support survey sweep synchron system tabl task tauro tdwi technolog term th therefor though thousand three thus time timestamp today togeth tool toward trade trade-off tradeoff tradit transact transaction-intens transform trend tri tudorica tupl turn tushar two type typic uma unbias under understand uniqu unlik unstructur up updat upon uri use usual util v valu various vast vector version version/revision vertic vertica viz vol voldemort volum wallach way websit weight well wilson within without work world worth written x xed xml y year yet z