Azure Data Explorer vs VictoriaMetrics

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 Azure Data Explorer and VictoriaMetrics so you can quickly see how they compare against each other.

The primary purpose of this article is to compare how Azure Data Explorer and VictoriaMetrics 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.

Azure Data Explorer Overview

Azure Data Explorer is a cloud-based, fully managed, big data analytics platform offered as part of the Microsoft Azure platform. It was announced by Microsoft in 2018 and is available as a PaaS offering. Azure Data Explorer provides high-performance capabilities for ingesting and querying telemetry, logs, and time series data.

VictoriaMetrics Overview

VictoriaMetrics is an open source time series database developed by the company VictoriaMetrics. The database aims to assist individuals and organizations in addressing their big data challenges by providing state-of-the-art monitoring and observability solutions. VictoriaMetrics is designed to be a fast, cost-effective, and scalable monitoring solution and time series database.

Azure Data Explorer for Time Series Data

Azure Data Explorer is well-suited for handling time series data. Its high-performance capabilities and ability to ingest large volumes of data make it suitable for analyzing and querying time series data in near real-time. With its advanced query operators, such as calculated columns, searching and filtering on rows, group by-aggregates, and joins, Azure Data Explorer enables efficient analysis of time series data. Its scalable architecture and distributed nature ensure that it can handle the velocity and volume requirements of time series data effectively.

VictoriaMetrics for Time Series Data

VictoriaMetrics is designed for time series data, making it a solid choice for applications that involve the storage and analysis of time-stamped data. It provides high-performance storage and retrieval capabilities, enabling efficient handling of large volumes of time series data.

Azure Data Explorer Key Concepts

• Relational Data Model: Azure Data Explorer is a distributed database based on relational database management systems. It supports entities such as databases, tables, functions, and columns. Unlike traditional RDBMS, Azure Data Explorer does not enforce constraints like key uniqueness, primary keys, or foreign keys. Instead, the necessary relationships are established at query time.
• Kusto Query Language (KQL): Azure Data Explorer uses KQL, a powerful and expressive query language, to enable users to explore and analyze their data with ease.
• Extents: In Azure Data Explorer, data is organized into units called extents, which are immutable, compressed sets of records that can be efficiently stored and queried.

VictoriaMetrics Key Concepts

• Time Series: VictoriaMetrics stores data in the form of time series, which are sequences of data points indexed by time.
• Metric: A metric represents a specific measurement or observation that is tracked over time.
• Tag: Tags are key-value pairs associated with a time series and are used for filtering and grouping data.
• Field: Fields contain the actual data values associated with a time series.
• Query Language: VictoriaMetrics supports its own query language, which allows users to retrieve and analyze time series data based on specific criteria.

Azure Data Explorer Architecture

Azure Data Explorer is built on a cloud-native, distributed architecture that supports both NoSQL and SQL-like querying capabilities. It is a columnar storage-based database that leverages compressed, immutable data extents for efficient storage and retrieval. The core components of Azure Data Explorer’s architecture include the Control Plane, Data Management, and Query Processing. The Control Plane is responsible for managing resources and metadata, while the Data Management component handles data ingestion and organization. Query Processing is responsible for executing queries and returning results to users.

VictoriaMetrics Architecture

VictoriaMetrics is available in two forms: Single-server-VictoriaMetrics and VictoriaMetrics Cluster. The Single-server-VictoriaMetrics is an all-in-one binary that is easy to use and maintain. It vertically scales well and can handle millions of metrics per second. On the other hand, VictoriaMetrics Cluster consists of components that allow for building horizontally scalable clusters, enabling high availability and scalability in demanding environments. The architecture of VictoriaMetrics enables users to choose the deployment option that best suits their needs and scale their database infrastructure as required.