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

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

PostgreSQL vs VictoriaMetrics Breakdown


 
Database Model

Relational database

Time series database

Architecture

PostgreSQL can be deployed on various platforms, such as on-premises, in virtual machines, or as a managed cloud service like Amazon RDS, Google Cloud SQL, or Azure Database for PostgreSQL.

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

PostgreSQL license (similar to MIT or BSD)

Apache 2.0

Use Cases

Web applications, geospatial data, business intelligence, analytics, content management systems, financial applications, scientific applications

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

Scalability

Supports vertical scaling, horizontal scaling through partitioning, sharding, and replication using available tools

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.

PostgreSQL Overview

PostgreSQL, also known as Postgres, is an open-source relational database management system that was first released in 1996. It has a long history of being a robust, reliable, and feature-rich database system, widely used in various industries and applications. PostgreSQL is known for its adherence to the SQL standard and extensibility, which allows users to define their own data types, operators, and functions. It is developed and maintained by a dedicated community of contributors and is available on multiple platforms, including Windows, Linux, and macOS.

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.


PostgreSQL for Time Series Data

PostgreSQL can be used for time series data storage and analysis, although it was not specifically designed for this use case. With its rich set of data types, indexing options, and window function support, PostgreSQL can handle time series data. However, Postgres will not be as optimized for time series data as specialized time series databases when it comes to things like data compression, write throughput, and query speed. PostgreSQL also lacks a number of features that are useful for working with time series data like downsampling, retention policies, and custom SQL functions for time series data analysis.

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.


PostgreSQL Key Concepts

  • MVCC: Multi-Version Concurrency Control is a technique used by PostgreSQL to allow multiple transactions to be executed concurrently without conflicts or locking.
  • WAL: Write-Ahead Logging is a method used to ensure data durability by logging changes to a journal before they are written to the main data files.
  • TOAST: The Oversized-Attribute Storage Technique is a mechanism for storing large data values in a separate table to reduce the main table’s disk space consumption.

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.


PostgreSQL Architecture

PostgreSQL is a client-server relational database system that uses the SQL language for querying and manipulation. It employs a process-based architecture, with each connection to the database being handled by a separate server process. This architecture provides isolation between different users and sessions. PostgreSQL supports ACID transactions and uses a combination of MVCC, WAL, and other techniques to ensure data consistency, durability, and performance. It also supports various extensions and external modules to enhance its functionality.

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.

PostgreSQL Features

Extensibility

PostgreSQL allows users to define custom data types, operators, and functions, making it highly adaptable to specific application requirements.

PostgreSQL has built-in support for full-text search, enabling users to perform complex text-based queries and analyses.

Geospatial support

With the PostGIS extension, PostgreSQL can store and manipulate geospatial data, making it suitable for GIS applications.

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.


PostgreSQL Use Cases

Enterprise applications

PostgreSQL is a popular choice for large-scale enterprise applications due to its reliability, performance, and feature set.

GIS applications

With the PostGIS extension, PostgreSQL can be used for storing and analyzing geospatial data in applications like mapping, routing, and geocoding.

OLTP workloads

As a relational database, PostgreSQL is a good fit for pretty much any application that involves transactional workloads.

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.


PostgreSQL Pricing Model

PostgreSQL is open source software, and there are no licensing fees associated with its use. However, costs can arise from hardware, hosting, and operational expenses when deploying a self-managed PostgreSQL server. Several cloud-based managed PostgreSQL services, such as Amazon RDS, Google Cloud SQL, and Azure Database for PostgreSQL, offer different pricing models based on factors like storage, computing resources, and support.

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.