Graphite vs TDengine

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

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

Graphite Overview

Graphite is an open-source monitoring and graphing tool created in 2006 by Orbitz and open sourced in 2008. Graphite is designed for storing time series data and is widely used for collecting, storing, and visualizing metrics from various sources, such as application performance, system monitoring, and business analytics.

TDengine Overview

TDengine is a high-performance, open source time series database designed to handle massive amounts of time series data efficiently. It was created by TAOS Data in 2017 and is specifically designed for Internet of Things (IoT), Industrial IoT, and IT infrastructure monitoring use cases. TDengine has a unique hybrid architecture that combines the advantages of both relational and NoSQL databases, providing high performance, easy-to-use SQL for querying, and flexible data modeling capabilities.

Graphite for Time Series Data

Graphite is specifically designed and optimized for time series data. It uses the Whisper database format, which efficiently stores and manages time series data by automatically aggregating and expiring data based on user-defined retention policies. Graphite supports a wide range of functions for querying, transforming, and aggregating time series data, enabling users to create custom graphs and dashboards. However, as Graphite focuses exclusively on time series data, it may not be suitable for other types of data or use cases that require more advanced data modeling or querying capabilities.

TDengine for Time Series Data

TDengine is designed from the ground up as a time series database, so it will be a good fit for most use cases that heavily involve storing and analyzing time series data.

Graphite Key Concepts

• Metric: A metric in Graphite represents a time series data point, consisting of a path (name), timestamp, and value.
• Series: A series is a collection of metrics that are all related to the same thing. For example, you might have a series for CPU usage, a series for memory usage, and a series for disk usage.
• Whisper: Whisper is a fixed-size, file-based time series database format used by Graphite. It automatically manages data retention and aggregation.
• Carbon: Carbon is the daemon responsible for receiving, caching, and storing metrics in Graphite. It listens for incoming metrics and writes them to Whisper files.
• Graphite-web: Graphite-web is the web application that provides a user interface for visualizing and querying the stored time series data.

TDengine Key Concepts

• Super Table: A template for creating multiple tables with the same schema. It’s similar to the concept of table inheritance in some other databases.
• Sub Table: A table created based on a Super Table, inheriting its schema. Sub Tables can have additional tags for categorization and querying purposes.
• Tag: A metadata attribute used to categorize and filter Sub Tables in a Super Table. Tags are indexed and optimized for efficient querying.

Graphite Architecture

Graphite’s architecture consists of several components, including Carbon, Whisper, and Graphite-web. Carbon is responsible for receiving metrics from various sources, caching them in memory, and storing them in Whisper files. Whisper is a file-based time series database format that efficiently manages data retention and aggregation. Graphite-web is the web application that provides a user interface for querying and visualizing the stored time series data. Graphite can be deployed on a single server or distributed across multiple servers for improved performance and scalability.

TDengine Architecture

TDengine uses a cloud native architecture that combines the advantages of relational databases (support for SQL querying) and NoSQL databases (scalability and flexibility).