DBMS > GreptimeDB vs. Microsoft Azure Table Storage vs. MySQL vs. VoltDB

System Properties Comparison GreptimeDB vs. Microsoft Azure Table Storage vs. MySQL vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An open source Time Series DBMS built for increased scalability, high performance and efficiency

A Wide Column Store for rapid development using massive semi-structured datasets

Widely used open source RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Time Series DBMS

Wide column store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.12
Rank	#351	Overall
	#34	Time Series DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

greptime.com

azure.microsoft.com/en-us/services/storage/tables

www.mysql.com

www.voltdb.com

Technical documentation

docs.greptime.com

dev.mysql.com/doc

docs.voltdb.com

Developer

Greptime Inc.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

VoltDB Inc.

Initial release

2022

2012

1995

2010

Current release

8.4.0, April 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Rust

C and C++

Java, C++

Server operating systems

Android
Docker
FreeBSD
Linux
macOS
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

for development

Data scheme

schema-free, schema definition possible

schema-free

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

gRPC
HTTP API
JDBC

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C++
Erlang
Go
Java
JavaScript

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Python

yes

proprietary syntax

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

optimistic locking

ACID

not for MyISAM storage engine

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Simple rights management via user accounts

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept

no user groups or roles

Users and roles with access to stored procedures

More information provided by the system vendor

Specific characteristics

GreptimeDB is a SQL & Python-enabled timeseries database system built from scratch...
» more

Competitive advantages

- Inherits advantages of Rust, such as excellent performance, memory safe, resource...
» more

Typical application scenarios

For IoT industries, GreptimeDB can seamless integrate with message queues and other...
» more

Key customers

Greptime's clients span multiple sectors including IoT, connected vehicles, and energy...
» more

Market metrics

GreptimeDB has garnered global recognition by topping GitHub trends following its...
» more

Licensing and pricing models

GreptimeDB: open source, distributed, cloud-native TSDB; supports Hybrid Time-series...
» more

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.