MongoDB vs StarRocks

Choosing the right database is a critical choice when building any software application. All databases have different strengths and weaknesses when it comes to performance, so deciding which database has the most benefits and the most minor downsides for your specific use case and data model is an important decision. Below you will find an overview of the key concepts, architecture, features, use cases, and pricing models of MongoDB and StarRocks so you can quickly see how they compare against each other.

The primary purpose of this article is to compare how MongoDB and StarRocks perform for workloads involving time series data, not for all possible use cases. Time series data typically presents a unique challenge in terms of database performance. This is due to the high volume of data being written and the query patterns to access that data. This article doesn’t intend to make the case for which database is better; it simply provides an overview of each database so you can make an informed decision.

MongoDB Overview

MongoDB is a popular, open-source NoSQL database launched in 2009. Designed to handle large volumes of unstructured and semi-structured data, MongoDB offers a flexible, schema-less data model, horizontal scalability, and high performance. Its ease of use, JSON-based document storage, and support for a wide range of programming languages have contributed to its widespread adoption across various industries and applications.

StarRocks Overview

StarRocks is an open source high-performance analytical data warehouse that enables real-time, multi-dimensional, and highly concurrent data analysis. It features an MPP (Massively Parallel Processing) architecture and is equipped with a fully vectorized execution engine and a columnar storage engine that supports real-time updates.

MongoDB for Time Series Data

Although MongoDB is a general-purpose NoSQL database, it can be used for storing and processing time series data. The flexible data model of MongoDB allows for easy adaptation to the evolving structure of time series data, such as the addition of new metrics or the modification of existing ones. MongoDB provides built-in support for time-to-live (TTL) indexes, which automatically expire old data after a specified time period, making it suitable for managing large volumes of time series data with a limited storage capacity. MongoDB has also recently added a custom columnar storage engine and time series collection for time series use cases, meant to improve performance over the default MongoDB storage engine in terms of data compression and query performance.

StarRocks for Time Series Data

StarRocks is primarily focused on data warehousing workloads but can be used for time series data. StarRocks can be used for real time analytics and historical data analysis.

MongoDB Key Concepts

Some key terminology and concepts specific to MongoDB include:

• Database: A MongoDB database is a container for collections, which are groups of related documents.
• Collection: A collection in MongoDB is analogous to a table in relational databases, holding a set of documents.
• Document: A document in MongoDB is a single record, stored in a JSON-like format called BSON (Binary JSON). Documents within a collection can have different structures.
• Field: A field is a key-value pair within a document, similar to an attribute or column in a relational database.
• Index: An index in MongoDB is a data structure that improves the query performance on specific fields within a collection.

StarRocks Key Concepts

• MPP Architecture: StarRocks utilizes an MPP architecture, which enables parallel processing and distributed execution of queries, allowing for high-performance and scalability.
• Vectorized Execution Engine: StarRocks employs a fully vectorized execution engine that leverages SIMD (Single Instruction, Multiple Data) instructions to process data in batches, resulting in optimized query performance.
• Columnar Storage Engine: The columnar storage engine in StarRocks organizes data by column, which improves query performance by only accessing the necessary columns during query execution.
• Cost-Based Optimizer (CBO): StarRocks includes a fully-customized cost-based optimizer that evaluates different query execution plans and selects the most efficient plan based on estimated costs.
• Materialized View: StarRocks supports intelligent materialized views, which are precomputed summaries of data that accelerate query performance by providing faster access to aggregated data.

MongoDB Architecture

MongoDB’s architecture is centered around its flexible, document-based data model. As a NoSQL database, MongoDB supports a schema-less structure, which allows for the storage and querying of diverse data types, such as nested arrays and documents. MongoDB can be deployed as a standalone server, a replica set, or a sharded cluster. Replica sets provide high availability through automatic failover and data redundancy, while sharded clusters enable horizontal scaling and load balancing by distributing data across multiple servers based on a shard key.

StarRocks Architecture

StarRock’s architecture includes a fully vectorized execution engine and a columnar storage engine for efficient data processing and storage. It also incorporates features like a cost-based optimizer and materialized views for optimized query performance. StarRocks supports real-time and batch data ingestion from a variety of sources and enables direct analysis of data stored in data lakes without data migration