November 2014 Summaries

This article discusses building an inexpensive petabyte database using MongoDB and Amazon Web Services (AWS). The authors chose to use spinning disk instances, which are cheaper than ephemeral storage options. They used AWS CloudWatch to monitor the cluster's performance and found that CPU was the bottleneck, not disk I/O. The authors also tested various query operations on a large dataset and found that they could achieve high query rates using parallel execution across the entire cluster. The article concludes by highlighting the potential for further scaling and optimization of MongoDB and invites readers to share their own experiences with scaling MongoDB implementations.

The text discusses the differences between building an application using SQL versus MongoDB for data storage and management. The author highlights that innovation in business and code has outpaced database technologies, leading to a need for more flexible and scalable solutions like MongoDB. The text compares the two approaches by considering the goals of capturing and processing data, as well as the complexity of storing and retrieving data. It notes that traditional RDBMS systems have limitations due to their rigid schema design, whereas MongoDB's flexible schema allows for easier adaptation to changing business needs. The author presents examples in Java to demonstrate how SQL and MongoDB differ in implementing simple tasks such as saving and fetching contact data, highlighting the benefits of MongoDB's rich query language and flexibility in addressing database queries.