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

The primary purpose of this article is to compare how AWS DynamoDB 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.

AWS DynamoDB vs VictoriaMetrics Breakdown


 
Database Model

Key-value and document store

Time series database

Architecture

DynamoDB is a fully managed, serverless NoSQL database provided by Amazon Web Services (AWS). It uses a single-digit millisecond latency for high-performance use cases and supports both key-value and document data models. Data is partitioned and replicated across multiple availability zones within an AWS region, and DynamoDB supports eventual or strong consistency for read operations

VictoriaMetrics can be deployed as a single-node instance for small-scale applications or as a clustered setup for large-scale applications, offering horizontal scalability and replication.

License

Closed source

Apache 2.0

Use Cases

Serverless web applications, real-time bidding platforms, gaming leaderboards, IoT data management, high-velocity data processing

Monitoring, observability, IoT, real-time analytics, DevOps, application performance monitoring

Scalability

Automatically scales to handle large amounts of read and write throughput, supports on-demand capacity and auto-scaling, global tables for multi-region replication

Horizontally scalable, supports clustering and replication for high availability and performance

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.

AWS DynamoDB Overview

Amazon DynamoDB is a managed NoSQL database service provided by AWS. It was first introduced in 2012, and it was designed to provide low-latency, high-throughput performance. DynamoDB is built on the principles of the Dynamo paper, which was published by Amazon engineers in 2007, and it aims to offer a highly available, scalable, and distributed key-value store.

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.


AWS DynamoDB for Time Series Data

DynamoDB can be used with time series data, although it may not be the most optimized solution compared to specialized time series databases. To store time series data in DynamoDB, you can use a composite primary key with a partition key for the entity identifier and a sort key for the timestamp. This allows you to efficiently query data for a specific entity and time range. However, DynamoDB’s main weakness when dealing with time series data is its lack of built-in support for data aggregation and downsampling, which are common requirements for time series analysis. You may need to perform these operations in your application or use additional services like AWS Lambda to process the data.

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.


AWS DynamoDB Key Concepts

Some of the key terms and concepts specific to DynamoDB include:

  • Tables: In DynamoDB, data is stored in tables, which are containers for items. Each table has a primary key that uniquely identifies each item in the table.
  • Items: Items are individual records in a DynamoDB table, and they consist of one or more attributes.
  • Attributes: Attributes are key-value pairs that make up an item in a table. DynamoDB supports scalar, document, and set data types for attributes.
  • Primary Key: The primary key uniquely identifies each item in a table, and it can be either a single-attribute partition key or a composite partition-sort key.

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.


AWS DynamoDB Architecture

DynamoDB is a NoSQL database that uses a key-value store and document data model. It is designed to provide high availability, durability, and scalability by automatically partitioning data across multiple servers and using replication to ensure fault tolerance. Some of the main components of DynamoDB include:

  • Partitioning: DynamoDB automatically partitions data based on the partition key, which ensures that data is evenly distributed across multiple storage nodes.
  • Replication: DynamoDB replicates data across multiple availability zones within an AWS region, providing high availability and durability.
  • Consistency: DynamoDB offers two consistency models: eventual consistency and strong consistency, allowing you to choose the appropriate level of consistency for your application.

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.

Free Time-Series Database Guide

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

AWS DynamoDB Features

Auto scaling

DynamoDB can automatically scale its read and write capacity based on the workload, allowing you to maintain consistent performance without over-provisioning resources.

Backup and restore

DynamoDB provides built-in support for point-in-time recovery, enabling you to restore your table to a previous state within the last 35 days.

Global tables

DynamoDB global tables enable you to replicate your table across multiple AWS regions, providing low-latency access and data redundancy for global applications.

Streams

DynamoDB Streams capture item-level modifications in your table and can be used to trigger AWS Lambda functions for real-time processing or to synchronize data with other AWS services.

VictoriaMetrics Features

High performance

VictoriaMetrics is optimized for high-performance storage and retrieval of time series data. It can efficiently handle millions of metrics per second and offers fast query execution for real-time analysis.

Scalability

The architecture of VictoriaMetrics allows for both vertical and horizontal scalability, enabling users to scale their monitoring and time series database infrastructure as their data volume and demand grow.

Cost-effectiveness

VictoriaMetrics provides a cost-effective solution for managing time series data. Its efficient storage and query capabilities contribute to minimizing operational costs while maintaining high performance.


AWS DynamoDB Use Cases

Session management

DynamoDB can be used to store session data for web applications, providing fast and scalable access to session information.

Gaming

DynamoDB can be used to store player data, game state, and other game-related information for online games, providing low-latency and high-throughput performance.

Internet of Things

DynamoDB can be used to store and process sensor data from IoT devices, enabling real-time monitoring and analysis of device data.

VictoriaMetrics Use Cases

Monitoring and Observability

VictoriaMetrics is widely used for monitoring and observability purposes, allowing organizations to collect, store, and analyze metrics and performance data from various systems and applications. It provides the necessary tools and capabilities to track and visualize key performance indicators, troubleshoot issues, and gain insights into system behavior.

IoT Data Management

VictoriaMetrics is suitable for handling large volumes of time series data generated by IoT devices. It can efficiently store and process sensor data, enabling real-time monitoring and analysis of IoT ecosystems. VictoriaMetrics allows for tracking and analyzing data from factories, manufacturing plants, satellites, and other IoT devices.

Capacity Planning

VictoriaMetrics enables retrospective analysis and forecasting of metrics for capacity planning purposes. It allows organizations to analyze historical data, identify patterns and trends, and make informed decisions about resource allocation and future capacity requirements.


AWS DynamoDB Pricing Model

DynamoDB offers two pricing options: provisioned capacity and on-demand capacity. With provisioned capacity, you specify the number of reads and writes per second that you expect your application to require, and you are charged based on the amount of provisioned capacity. This pricing model is suitable for applications with predictable traffic or gradually ramping traffic. You can use auto scaling to adjust your table’s capacity automatically based on the specified utilization rate, ensuring application performance while reducing costs.

On the other hand, with on-demand capacity, you pay per request for the data reads and writes your application performs on your tables. You do not need to specify how much read and write throughput you expect your application to perform, as DynamoDB instantly accommodates your workloads as they ramp up or down. This pricing model is suitable for applications with fluctuating or unpredictable traffic patterns.

VictoriaMetrics Pricing Model

VictoriaMetrics is an open source project, which means it is available for free usage and doesn’t require any licensing fees. Users can download the binary releases, Docker images, or source code to set up and deploy VictoriaMetrics without incurring any direct costs. VictoriaMetrics also has paid offerings for on-prem Enterprise products and managed VictoriaMetrics instances.