DBMS > Graph Engine vs. MySQL vs. SAP HANA vs. VictoriaMetrics

System Properties Comparison Graph Engine vs. MySQL vs. SAP HANA vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Widely used open source RDBMS

In-memory, column based data store. Available as appliance or cloud service

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	1.23
Rank	#165	Overall
	#15	Time Series DBMS

Website

www.graphengine.io

www.mysql.com

www.sap.com/products/hana.html

victoriametrics.com

Technical documentation

www.graphengine.io/docs/manual

dev.mysql.com/doc

help.sap.com/hana

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

SAP

VictoriaMetrics

Initial release

2010

1995

2010

2018

Current release

9.0.0, July 2024

2.0 SPS07 (April 4, 2023), April 2023

v1.91, May 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

.NET and C

C and C++

Server operating systems

.NET

FreeBSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

FreeBSD
Linux
macOS
OpenBSD

Data scheme

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

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

C#
C++
F#
Visual Basic

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

Server-side scripts

Stored procedures

yes

proprietary syntax

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

yes

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.