Comparing NoSQL MongoDB to an SQL DB

Authors:
Zachary Parker;Scott Poe;Susan V. Vrbsky
Affiliations:
The University of Alabama, Tuscaloosa, AL;The University of Alabama, Tuscaloosa, AL;The University of Alabama, Tuscaloosa, AL
Venue:
Proceedings of the 51st ACM Southeast Conference
Year:
2013

Citing 4
Cited 0

MapReduce: simplified data processing on large clusters

OSDI'04 Proceedings of the 6th conference on Symposium on Opearting Systems Design & Implementation - Volume 6
SQL databases v. NoSQL databases

Communications of the ACM
Will NoSQL Databases Live Up to Their Promise?

Computer
NoSQL evaluation: A use case oriented survey

CSC '11 Proceedings of the 2011 International Conference on Cloud and Service Computing

Quantified Score

Hi-index	0.00

Visualization

Abstract

NoSQL database solutions are becoming more and more prevalent in a world currently dominated by SQL relational databases. NoSQL databases were designed to provide database solutions for large volumes of data that is not structured. However, the advantages (or disadvantages) of using a NoSQL database for data that is structured, and not necessarily "Big," is not clear. There are not many studies that compare the performance of processing a modest amount of structured data in a NoSQL database with a traditional relational database. In this paper, we compare one of the NoSQL solutions, MongoDB, to the standard SQL relational database, SQL Server. We compare the performance, in terms of runtime, of these two databases for a modest-sized structured database. Results show that MongoDB performs equally as well or better than the relational database, except when aggregate functions are utilized.