DBMS > Memgraph vs. Riak KV vs. Teradata

System Properties Comparison Memgraph vs. Riak KV vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A hybrid, in-memory first, distributed graph DBMS delivering high-performance on analytical and transactional workloads at enterprise scale

Distributed, fault tolerant key-value store

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Graph DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Document store
Graph DBMS
Time Series DBMS

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

Score	0.08
Rank	#305	Overall
	#29	Graph DBMS

Score	5.34
Rank	#67	Overall
	#9	Key-value stores

Score	72.59
Rank	#14	Overall
	#9	Relational DBMS

Website

memgraph.com

riak.com/products/riak-kv

www.teradata.com

Technical documentation

docs.memgraph.com

docs.teradata.com

Developer

Memgraph Ltd

Basho Technologies

Teradata

Initial release

2017

2009

1984

Current release

2.1.0, April 2015

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Free license available

Open Source

Apache version 2, commercial enterprise edition

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

Erlang

Server operating systems

Linux

Linux
OS X

hosted
Linux

Data scheme

schema-free and schema-optional

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

restricted

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL 2016 + extensions

APIs and other access methods

Bolt protocol
Cypher query language

HTTP API
Native Erlang Interface

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

.Net
C
C++
Elixir
Go
Haskell
Java
JavaScript
PHP
Python
Ruby
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

JavaScript and Erlang

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

dynamic graph partitioning

Sharding

no "single point of failure"

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

links between data sets can be stored

yes

Transaction concepts

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

ACID

with snapshot isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

with periodic snapshot and write-ahead logging (WAL) of changes

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, roles and permissions

fine grained access rights according to SQL-standard

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.