DBMS > OrigoDB vs. SAP HANA vs. TerminusDB vs. Vitess

System Properties Comparison OrigoDB vs. SAP HANA vs. TerminusDB vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Object oriented DBMS

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
RDF store

Document store
Spatial DBMS

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

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

origodb.com

www.sap.com/products/hana.html

terminusdb.com

vitess.io

Technical documentation

origodb.com/docs

help.sap.com/hana

terminusdb.github.io/terminusdb/#

vitess.io/docs

Developer

Robert Friberg et al

SAP

DataChemist Ltd.

The Linux Foundation, PlanetScale

Initial release

2009

under the name LiveDB

2010

2018

2013

Current release

2.0 SPS07 (April 4, 2023), April 2023

11.0.0, January 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

commercial

Open Source

GPL V3

Open Source

Apache Version 2.0, commercial licenses available

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

Prolog, Rust

Server operating systems

Linux
Windows

Appliance or cloud-service

Linux

Docker
Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

SQL-like query language (WOQL)

yes

with proprietary extensions

APIs and other access methods

.NET Client API
HTTP API
LINQ

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net

JavaScript
Python

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

SQLScript, R

yes

proprietary syntax

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

yes

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Journaling Streams

Multi-source replication
Source-replica 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 across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

depending on model

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

yes

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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.