DBMS > KeyDB vs. SAP HANA vs. Teradata vs. TerminusDB vs. VelocityDB

System Properties Comparison KeyDB vs. SAP HANA vs. Teradata vs. TerminusDB vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

A hybrid cloud data analytics software platform (Teradata Vantage)

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Key-value store

Relational DBMS

Graph DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

www.sap.com/products/hana.html

www.teradata.com

terminusdb.com

velocitydb.com

Technical documentation

docs.keydb.dev

help.sap.com/hana

docs.teradata.com

terminusdb.github.io/terminusdb/#

velocitydb.com/UserGuide

Developer

EQ Alpha Technology Ltd.

SAP

Teradata

DataChemist Ltd.

VelocityDB Inc

Initial release

2019

2010

1984

2018

2011

Current release

2.0 SPS07 (April 4, 2023), April 2023

Teradata Vantage 1.0 MU2, January 2019

11.0.0, January 2023

7.x

License

Commercial or Open Source

Open Source

BSD-3

commercial

Open Source

GPL V3

commercial

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

C++

Prolog, Rust

Server operating systems

Linux

Appliance or cloud-service

hosted
Linux

Linux

Any that supports .NET

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

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

yes

SQL

Support of SQL

yes

SQL 2016 + extensions

SQL-like query language (WOQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

.Net

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

JavaScript
Python

.Net

Server-side scripts

Stored procedures

Lua

SQLScript, R

yes

UDFs, stored procedures, table functions in parallel

yes

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Hashing

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

in-memory journaling

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

simple password-based access control and ACL

yes

fine grained access rights according to SQL-standard

Role-based access control

Based on Windows Authentication

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.