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 Apache Doris and M3 so you can quickly see how they compare against each other.

The primary purpose of this article is to compare how Apache Doris and M3 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.

Apache Doris vs M3 Breakdown


 
Database Model

Data warehouse

Time series database

Architecture

Doris can be deployed on-premises or in the cloud and is compatible with various data formats such as Parquet, ORC, and JSON.

The M3 stack can be deployed on-premises or in the cloud, using containerization technologies like Kubernetes or as a managed service on platforms like AWS or GCP

License

Apache 2.0

Apache 2.0

Use Cases

Interactive analytics, data warehousing, real-time data analysis, reporting, dashboarding

Monitoring, observability, IoT, Real-time analytics, large-scale metrics processing

Scalability

Horizontally scalable with distributed storage and compute

Horizontally scalable, designed for high availability and large-scale deployments

Looking for the most efficient way to get started?

Whether you are looking for cost savings, lower management overhead, or open source, InfluxDB can help.

Apache Doris Overview

Apache Doris is an MPP-based interactive SQL data warehousing system designed for reporting and analysis. It is known for its high performance, real-time analytics capabilities, and ease of use. Apache Doris integrates technologies from Google Mesa and Apache Impala. Unlike other SQL-on-Hadoop systems, Doris is designed to be a simple and tightly coupled system that does not rely on external dependencies. It aims to provide a streamlined and efficient solution for data warehousing and analytics.

M3 Overview

M3 is a distributed time series database written entirely in Go. It is designed to collect a high volume of monitoring time series data, distribute storage in a horizontally scalable manner, and efficiently leverage hardware resources. M3 was initially developed by Uber as a scalable remote storage backend for Prometheus and Graphite and later open-sourced for broader use.


Apache Doris for Time Series Data

Apache Doris can be effectively used with time series data for real-time analytics and reporting. With its high performance and sub-second response time, Doris can handle massive amounts of time-stamped data and provide timely query results. It supports both high-concurrent point query scenarios and high-throughput complex analysis scenarios, making it suitable for analyzing time series data with varying levels of complexity.

M3 for Time Series Data

M3 is specifically designed for time-series data. It is a distributed and scalable time-series database optimized for handling large volumes of high-resolution data points, making it an ideal solution for storing, querying, and analyzing time-series data.

M3’s architecture focuses on providing fast and efficient querying capabilities, as well as high ingestion rates, which are essential for working with time-series data. Its horizontal scalability and high availability ensure that it can handle the demands of large-scale deployments and maintain performance as data volumes grow.


Apache Doris Key Concepts

  • MPP (Massively Parallel Processing): Apache Doris leverages MPP architecture, which allows it to distribute data processing across multiple nodes, enabling parallel execution and scalability.
  • SQL: Apache Doris supports SQL as the query language, providing a familiar and powerful interface for data analysis and reporting.
  • Point Query: Point query refers to retrieving a specific data point or a small subset of data from the database.
  • Complex Analysis: Apache Doris can handle complex analysis scenarios that involve processing large volumes of data and performing advanced computations and aggregations.

M3 Key Concepts

  • Time Series Compression: M3 has the ability to compress time series data, resulting in significant memory and disk savings. It uses two compression algorithms, M3TSZ and protobuf encoding, to achieve efficient data compression.
  • Sharding: M3 uses virtual shards that are assigned to physical nodes. Timeseries keys are hashed to a fixed set of virtual shards, making horizontal scaling and node management seamless.
  • Consistency Levels: M3 provides variable consistency levels for read and write operations, as well as cluster connection operations. Write consistency levels include One (success of a single node), Majority (success of the majority of nodes), and All (success of all nodes). Read consistency level is One, which corresponds to reading from a single nod


Apache Doris Architecture

Apache Doris is based on MPP architecture, which enables it to distribute data and processing across multiple nodes for parallel execution. It is a standalone system and does not depend on other systems or frameworks. Apache Doris combines the technology of Google Mesa and Apache Impala to provide a simple and tightly coupled system for data warehousing and analytics. It leverages SQL as the query language and supports efficient data processing and query optimization techniques to ensure high performance and scalability.

M3 Architecture

M3 is designed to be horizontally scalable and handle high data throughput. It uses fileset files as the primary unit of long-term storage, storing compressed streams of time series values. These files are flushed to disk after a block time window becomes unreachable. M3 has a commit log, equivalent to the commit log or write-ahead-log in other databases, which ensures data integrity. Client Peer streaming is responsible for fetching blocks from peers for bootstrapping purposes. M3 also implements caching policies to optimize efficient reads by determining which flushed blocks are kept in memory.

Free Time-Series Database Guide

Get a comprehensive review of alternatives and critical requirements for selecting yours.

Apache Doris Features

High Performance

Apache Doris is designed for high-performance data analytics, delivering sub-second query response times even with massive amounts of data.

Real-Time Analytics

Apache Doris enables real-time data analysis, allowing users to gain insights and make informed decisions based on up-to-date information.

Scalability

Apache Doris can scale horizontally by adding more nodes to the cluster, allowing for increased data storage and processing capacity.

M3 Features

Commit Log

M3 uses a commit log to ensure data integrity, providing durability for write operations.

Peer Streaming

M3’s client peer streaming fetches data blocks from peers for bootstrapping purposes, optimizing data retrieval and distribution.

Caching Mechanisms

M3 implements various caching policies to efficiently manage memory usage, keeping frequently accessed data blocks in memory for faster reads.


Apache Doris Use Cases

Real-Time Analytics

Apache Doris is well-suited for real-time analytics scenarios where timely insights and analysis of large volumes of data are crucial. It enables businesses to monitor and analyze real-time data streams, make data-driven decisions, and detect patterns or anomalies in real time.

Reporting and Business Intelligence

Apache Doris can be used for generating reports and conducting business intelligence activities. It supports fast and efficient querying of data, allowing users to extract meaningful insights and visualize data for reporting and analysis purposes.

Data Warehousing

Apache Doris is suitable for building data warehousing solutions that require high-performance analytics and querying capabilities. It provides a scalable and efficient platform for storing, managing, and analyzing large volumes of data for reporting and decision-making.

M3 Use Cases

Monitoring and Observability

M3 is particularly suitable for large-scale monitoring and observability tasks, as it can store and manage massive volumes of time-series data generated by infrastructure, applications, and microservices. Organizations can use M3 to analyze, visualize, and detect anomalies in the metrics collected from various sources, enabling them to identify potential issues and optimize their systems.

IoT and Sensor Data

M3 can be used to store and process the vast amounts of time-series data generated by IoT devices and sensors. By handling data from millions of devices and sensors, M3 can provide organizations with valuable insights into the performance, usage patterns, and potential issues of their connected devices. This information can be used for optimization, predictive maintenance, and improving the overall efficiency of IoT systems.

Financial Data Analysis

Financial organizations can use M3 to store and analyze time-series data related to stocks, bonds, commodities, and other financial instruments. By providing fast and efficient querying capabilities, M3 can help analysts and traders make more informed decisions based on historical trends, current market conditions, and potential future developments.


Apache Doris Pricing Model

As an open-source project, Apache Doris is freely available for usage and does not require any licensing fees. Users can download the source code and set up Apache Doris on their own infrastructure without incurring any direct costs. However, it’s important to consider the operational costs associated with hosting and maintaining the database infrastructure.

M3 Pricing Model

M3 is an open source database and can be used freely, although you will have to account for the cost of managing your infrastructure and the hardware used to run M3. Chronosphere is the co-maintainer of M3 along with Uber and also offers a hosted observability that uses M3 as the backend storage layer.