DBMS > mSQL vs. OrigoDB vs. SAP HANA vs. TerminusDB vs. Warp 10

System Properties Comparison mSQL vs. OrigoDB vs. SAP HANA vs. TerminusDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Graph DBMS

Time Series 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	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

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

hughestech.com.au/products/msql

origodb.com

www.sap.com/products/hana.html

terminusdb.com

www.warp10.io

Technical documentation

origodb.com/docs

help.sap.com/hana

terminusdb.github.io/terminusdb/#

www.warp10.io/content/02_Getting_started

Developer

Hughes Technologies

Robert Friberg et al

SAP

DataChemist Ltd.

SenX

Initial release

1994

2009

under the name LiveDB

2010

2018

2015

Current release

4.4, October 2021

2.0 SPS07 (April 4, 2023), April 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

commercial

Open Source

GPL V3

Open Source

Apache License 2.0

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

Java

Server operating systems

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

Linux
Windows

Appliance or cloud-service

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

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

JDBC
ODBC

.NET Client API
HTTP API
LINQ

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

HTTP API
Jupyter
WebSocket

Supported programming languages

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

JavaScript
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

yes

WarpScript

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

yes

Graph Partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

Journaling Streams

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.