DBMS > HugeGraph vs. Memcached vs. SAP HANA vs. VoltDB

System Properties Comparison HugeGraph vs. Memcached vs. SAP HANA vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fast-speed and highly-scalable Graph DBMS

In-memory key-value store, originally intended for caching

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

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

Graph DBMS

Key-value store

Relational DBMS

Secondary database models

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.13
Rank	#336	Overall
	#32	Graph DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

github.com/hugegraph
hugegraph.apache.org

www.memcached.org

www.sap.com/products/hana.html

www.voltdb.com

Technical documentation

hugegraph.apache.org/docs

github.com/memcached/memcached/wiki

help.sap.com/hana

docs.voltdb.com

Developer

Baidu

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SAP

VoltDB Inc.

Initial release

2018

2003

2010

Current release

0.9

1.6.25, March 2024

2.0 SPS07 (April 4, 2023), April 2023

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSD license

commercial

Open Source

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

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

Java

Java, C++

Server operating systems

Linux
macOS
Unix

FreeBSD
Linux
OS X
Unix
Windows

Appliance or cloud-service

Linux
OS X

for development

Data scheme

yes

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.

Secondary indexes

yes

also supports composite index and range index

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

Proprietary protocol

JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Groovy
Java
Python

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

SQLScript, R

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

none

Repcached, a Memcached patch, provides this functionallity

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

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

Users, roles and permissions

yes

using SASL (Simple Authentication and Security Layer) protocol

yes

Users and roles with access to stored procedures

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.