DBMS > KeyDB vs. mSQL vs. OrigoDB vs. SAP HANA vs. TerminusDB

System Properties Comparison KeyDB vs. mSQL vs. OrigoDB vs. SAP HANA vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

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

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

Primary database model

Key-value store

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial 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	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

hughestech.com.au/products/msql

origodb.com

www.sap.com/products/hana.html

terminusdb.com

Technical documentation

docs.keydb.dev

origodb.com/docs

help.sap.com/hana

terminusdb.github.io/terminusdb/#

Developer

EQ Alpha Technology Ltd.

Hughes Technologies

Robert Friberg et al

SAP

DataChemist Ltd.

Initial release

2019

1994

2009

under the name LiveDB

2010

2018

Current release

4.4, October 2021

2.0 SPS07 (April 4, 2023), April 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

BSD-3

commercial

free licenses can be provided

Open Source

commercial

Open Source

GPL V3

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

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Appliance or cloud-service

Linux

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

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL-like query language (WOQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC

.NET Client API
HTTP API
LINQ

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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++
Delphi
Java
Perl
PHP
Tcl

.Net

JavaScript
Python

Server-side scripts

Stored procedures

Lua

yes

SQLScript, R

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication

yes

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

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

yes

in-memory journaling

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

Role based authorization

yes

Role-based access control

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.