DBMS > MySQL vs. RavenDB vs. TimescaleDB vs. UniData,UniVerse vs. Vertica

System Properties Comparison MySQL vs. RavenDB vs. TimescaleDB vs. UniData,UniVerse vs. Vertica

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

MultiValue database and application server with SQL mapping layer and meta database capabilities

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Relational DBMS

Key/Value like access via memcached API

Column oriented

Secondary database models

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Score	2.25
Rank	#112	Overall
	#2	Multivalue DBMS

Score	9.62
Rank	#42	Overall
	#26	Relational DBMS

Website

www.mysql.com

ravendb.net

www.timescale.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

www.vertica.com

Technical documentation

dev.mysql.com/doc

ravendb.net/docs

docs.timescale.com

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

vertica.com/documentation

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Hibernating Rhinos

Timescale

Rocket Software

OpenText

previously Micro Focus and Hewlett Packard

Initial release

1995

2010

2017

1985

2005

Current release

9.0.0, July 2024

5.4, July 2022

2.15.0, May 2024

12.0.3, January 2023

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL version 3, commercial license available

Open Source

Apache 2.0

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

schema-free

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

optional

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

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (RQL)

yes

full PostgreSQL SQL syntax

yes

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

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

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

.Net
Basic

U2 Basic
C
Java

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

yes

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

U2 Basic

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

yes, across time and space (hash partitioning) attributes

none

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Source-replica replication with hot standby and reads on replicas

Source-replica replication

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID, Cluster-wide transaction available

ACID

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

Access rights according to SQL-standard and operating system based

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

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.