Amazon Timestream for LiveAnalytics vs M3

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 Amazon Timestream for LiveAnalytics and M3 so you can quickly see how they compare against each other.

The primary purpose of this article is to compare how Amazon Timestream for LiveAnalytics 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.

Amazon Timestream for LiveAnalytics Overview

Amazon Timestream for LiveAnalytics is a fully managed, serverless time series database service developed by Amazon Web Services (AWS). Launched in 2020, Amazon Timestream for LiveAnalytics is designed specifically for handling time series data, making it an ideal choice for IoT, monitoring, and analytics applications that require high ingestion rates, efficient storage, and fast querying capabilities. As a part of the AWS ecosystem, Timestream seamlessly integrates with other AWS services, simplifying the process of building and deploying time series applications in the cloud.

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.

Amazon Timestream for LiveAnalytics for Time Series Data

Amazon Timestream for LiveAnalytics is designed specifically for handling time series data, making it a suitable choice for a wide range of applications that require high ingestion rates, efficient storage, and fast querying capabilities. Its dual-tiered storage architecture, consisting of the Memory Store and Magnetic Store, allows Timestream to automatically manage data retention and optimize storage costs based on data age and access patterns. Additionally, Timestream supports SQL-like querying and integrates with popular analytics tools, making it easy for users to gain insights from their time series data.

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.

Amazon Timestream for LiveAnalytics Key Concepts

• Memory Store: In Amazon Timestream for LiveAnalytics, the Memory Store is a component that stores recent, mutable time series data in memory for fast querying and analysis.
• Magnetic Store: The Magnetic Store in Amazon Timestream for LiveAnalytics is responsible for storing historical, immutable time series data on disk for cost-efficient, long-term storage.
• Time-to-Live (TTL): Amazon Timestream for LiveAnalytics allows users to set a TTL on their time series data, which determines how long data is retained in the Memory Store before being moved to the Magnetic Store or deleted.

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

Amazon Timestream for LiveAnalytics Architecture

Amazon Timestream for LiveAnalytics is built on a serverless, distributed architecture that supports SQL-like querying capabilities. Its data model is specifically tailored for time series data, using time-stamped records and a flexible schema that can accommodate varying data granularities and dimensions. The core components of Timestream’s architecture include the Memory Store and the Magnetic Store, which together manage data retention, storage, and querying. The Memory Store is optimized for fast querying of recent data, while the Magnetic Store provides cost-efficient, long-term storage for historical 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.