M3 vs AWS Redshift
A detailed comparison
Compare M3 and AWS Redshift for time series and OLAP workloads
Learn About Time Series DatabasesChoosing 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 M3 and AWS Redshift so you can quickly see how they compare against each other.
The primary purpose of this article is to compare how M3 and AWS Redshift 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.
M3 vs AWS Redshift Breakdown
 |
 |
|
| Database Model | Time series database |
Data warehouse |
| Architecture | 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 |
AWS Redshift utilizes a columnar storage format for fast querying and supports standard SQL. Redshift uses a distributed, shared-nothing architecture, where data is partitioned across multiple compute nodes. Each node is further divided into slices, with each slice processing a subset of data in parallel. Redshift can be deployed in a single-node or multi-node cluster, with the latter providing better performance for large datasets. |
| License | Apache 2.0 |
Closed source |
| Use Cases | Monitoring, observability, IoT, Real-time analytics, large-scale metrics processing |
Business analytics, large-scale data processing, real-time dashboards, data integration, machine learning |
| Scalability | Horizontally scalable, designed for high availability and large-scale deployments |
Supports scaling storage and compute independently, with support for adding or removing nodes as needed |
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.
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.
AWS Redshift Overview
Amazon Redshift is a fully managed, petabyte-scale data warehouse service in the cloud. It was launched in 2012 as part of the AWS suite of products. Redshift is designed for analytic workloads and integrates with various data loading and ETL tools, as well as business intelligence and reporting tools. It uses columnar storage to optimize storage costs and improve query performance.
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.
AWS Redshift for Time Series Data
AWS Redshift can be used for time series data workloads, although Redshift is optimized for more general data warehouse use cases. Users can utilize date and time-based functions to aggregate, filter, and transform time series data. Redshift also offers ‘time-series tables’ which allow data to be stored in tables based on a fixed retention period.
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
AWS Redshift Key Concepts
- Cluster: A Redshift cluster is a set of nodes, which consists of a leader node and one or more compute nodes. The leader node manages communication with client applications and coordinates query execution among compute nodes.
- Compute Node: These nodes store data and execute queries in parallel. The number of compute nodes in a cluster affects its storage capacity and query performance.
- Columnar Storage: Redshift uses a columnar storage format, which stores data in columns rather than rows. This format improves query performance and reduces storage space requirements.
- Node slices: Compute nodes are divided into slices. Each slice is allocated an equal portion of the node’s memory and disk space, where it processes a portion of the loaded data.
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.
AWS Redshift Architecture
Redshift’s architecture is based on a distributed and shared-nothing architecture. A cluster consists of a leader node and one or more compute nodes. The leader node is responsible for coordinating query execution, while compute nodes store data and execute queries in parallel. Data is stored in a columnar format, which improves query performance and reduces storage space requirements. Redshift uses Massively Parallel Processing (MPP) to distribute and execute queries across multiple nodes, allowing it to scale horizontally and provide high performance for large-scale data warehousing workloads.
Free Time-Series Database Guide
Get a comprehensive review of alternatives and critical requirements for selecting yours.
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.
AWS Redshift Features
Scalability
Redshift allows you to scale your cluster up or down by adding or removing compute nodes, enabling you to adjust your storage capacity and query performance based on your needs.
Performance
Redshift’s columnar storage format and MPP architecture enable it to deliver high-performance query execution for large-scale data warehousing workloads.
Security
Redshift provides a range of security features, including encryption at rest and in transit, network isolation using Amazon Virtual Private Cloud (VPC), and integration with AWS Identity and Access Management (IAM) for access control.
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.
AWS Redshift Use Cases
Data Warehousing
Redshift is designed for large-scale data warehousing workloads, providing a scalable and high-performance solution for storing and analyzing structured data.
Business Intelligence and Reporting
Redshift integrates with various BI and reporting tools, enabling organizations to gain insights from their data and make data-driven decisions.
ETL and Data Integration
Redshift supports data loading and extraction, transformation, and loading (ETL) processes, allowing you to integrate data from various sources and prepare it for analysis.
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.
AWS Redshift Pricing Model
Amazon Redshift offers two pricing models: On-Demand and Reserved Instances. With On-Demand pricing, you pay for the capacity you use on an hourly basis, with no long-term commitments. Reserved Instances offer the option to reserve capacity for a one- or three-year term, with a lower hourly rate compared to On-Demand pricing. In addition to these pricing models, you can also choose between different node types, which offer different amounts of storage, memory, and compute resources.
Get started with InfluxDB for free
InfluxDB Cloud is the fastest way to start storing and analyzing your time series data.
