Nosql Databases Live Up To Their Promise  Essay

PAGES
2
WORDS
680
Cite

¶ … NoSQL Databases Live Up TO Their Promise? (Leavitt, 2010) the author presents a fair and balanced analysis of the NoSQL database technologies and supporting Big Data platforms including Cassandra and HBase (the precursor of Hadoop) with accuracy and clarity. The author also points out that despite the cost advantages of NoSQL and its inherent strengths in managing massive amount of unstructured content, its limitations from an enterprise computing perspective including overhead and complexity, consistency including support for atomicity of data and support for the industry-wide ACID framework are lacking (Leavitt, 2010). The comparison of SQL vs. NoSQL database technologies is well-done in the article, pointing out how NoSQL excels at managing object-, image and textually-based data while the former excels at structured data and the speed of transactions. The article does not mention however how the complexities of managing batch-oriented processes of very large data sets vary between the two database technologies (Stonebraker, 2010). What differentiates NoSQL databases the most however are the key-value stores, approach to defining...

...

These innate strengths of NoSQL databases and the exponential increase in content generated daily on social networking sites will eventually lead to NoSQL being a foundational element of Big Data strategies across the enterprise. Using multiple databases unified by a common data model (Ghosh, 2010).
For all of these strengths in the article however, there are several shortcoming including the following. First, the article doesn't fully address just how much more robust NoSQL is at managing analytics functions and the development, scaling across multiple virtual machines including integration to Sold State Drives (SSDs) as Amazon Dynamo's architecture supports today (Rys, 2011). Second, the role of Latent Semantic Indexing (LSI) and its role in the Google algorithm, parsing of data within the LinkedIn Big Data and data scientist initiatives designed provide greater accuracy of results to searches and ad hoc network analysis are making NoSQL emerge as a more…

Sources Used in Documents:

References

Ghosh, D. (2010). Multiparadigm data storage for enterprise applications. IEEE Software, 27(5), 57-60.

Leavitt, N. (2010, February ). Will NoSQL databases live up to their promise?. COMPUTER Journal by IEEE Society, 12-14. Retrieved from http://www.leavcom.com/pdf/NoSQL.pdf

Meijer, E., & Bierman, G. (2011). A co-relational model of data for large shared data banks. Association for Computing Machinery.Communications of the ACM, 54(4), 49.

Rys, M. (2011). Scalable SQL. Association for Computing Machinery.Communications of the ACM, 54(6), 48.


Cite this Document:

"Nosql Databases Live Up To Their Promise " (2012, January 21) Retrieved April 18, 2024, from
https://www.paperdue.com/essay/nosql-databases-live-up-to-their-promise-77559

"Nosql Databases Live Up To Their Promise " 21 January 2012. Web.18 April. 2024. <
https://www.paperdue.com/essay/nosql-databases-live-up-to-their-promise-77559>

"Nosql Databases Live Up To Their Promise ", 21 January 2012, Accessed.18 April. 2024,
https://www.paperdue.com/essay/nosql-databases-live-up-to-their-promise-77559

Related Documents

Relational Databases For each table, identify the primary key and the foreign key(s). If a table does not have a foreign key, write None in the space provided. PRIMARY KEY FOREIGN KEY Truck TRUCK_NUM BASE_CODE, TYPE_CODE Base BASE_CODE TYPE_CODE Do the tables exhibit entity integrity? Answer yes or no, and then explain your answer. ENTITY INTEGRITY EXPLANATION Truck All rows under the primary key TRUCK_NUM are uniquely identified and there are no null entries Base All rows under the primary key BASE_CODE are uniquely identified and

Relational Databases in e-Commerce Of the many uses of relational databases throughout enterprise software their use for supporting e-commerce initiatives and programs provides a foundation for assessing their performance at diverse data and taxonomy management, and scalability of transactions as well. The scalability, security and speed of relational databases when used for e-commerce tasks push them to the limits of performance and customization as well. An example of this is the

This is one of the greatest limitations of this technology. A second major disadvantage of RDBMS-based systems is their lack of support for image- and spatial-based databases that include Computer-Aided Design (CAD) drawings, 3D rendering and model-based data. Their table-based structure is inefficient in defining the attributes of these data types and lacks the necessary data tagging and data types to manage imaging and CAD-based design files and data

They in short link and map ideas that already exist, creating real time answers to questions as they are applied to new and archived knowledge or action plans. According to IDC reports, most data warehouses will be stored in a columnar fashion and not in rows, reporting and data collection problems will be solved with databases that have no formal schema at all, horizontal scalability through clustering will be achieved

Standard-Relational and Object-Relational Databases Software development has experienced evolution over the past few decades given the increasing demands for better information systems in today's society, especially in the modern business environment. The evolution of software development during this period has also been influenced by the tremendous changes in the ways with which computers are used and programmed. The changes in software development have contributed to the emergence of different categories of

" "STUDENT INFORMATION TABLE" ( "STUDENT ID" CHARACTER (4) NOT NULL, NAME CHARACTER (25) NOT NULL, "STREET NUMBER" CHARACTER (10) NOT NULL, "STREET NAME" CHARACTER (25) NOT NULL, CITY CHARACTER (25) NOT NULL, STATE CHARACTER (10) NOT NULL, EMAIL CHARACTER (25) NOT NULL, "PHONE NUMBER" CHARACTER (15) NOT NULL ); CONNECT RESET; SQL FOR Book_Information CONNECT TO LIBRARY; CREATE TABLE "USER"; CREATE TABLE BookInformation ( "BookISBN" CHARACTER (10) NOT NULL; "AUTHOR" CHARACTER (25) NOT NULL; "TITLE" CHARACTER (50) NOT NULL; "PRICE" CHARACTER (10) NOT NULL; CONNECT RESET; SQL STATEMENT FOR