DBMS > gStore vs. mSQL vs. OrigoDB vs. SAP HANA

System Properties Comparison gStore vs. mSQL vs. OrigoDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A native Graph DBMS to store and maintain very large RDF datasets.

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

Primary database model

Graph DBMS
RDF store

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.04
Rank	#359	Overall
	#37	Graph DBMS
	#18	RDF 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

Website

en.gstore.cn

hughestech.com.au/products/msql

origodb.com

www.sap.com/products/hana.html

Technical documentation

en.gstore.cn/#/enDocs

origodb.com/docs

help.sap.com/hana

Developer

Hughes Technologies

Robert Friberg et al

SAP

Initial release

2016

1994

2009

under the name LiveDB

2010

Current release

1.2, November 2023

4.4, October 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

BSD

commercial

free licenses can be provided

Open Source

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++

Server operating systems

Linux

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

Linux
Windows

Appliance or cloud-service

Data scheme

schema-free and OWL/RDFS-schema support

yes

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

APIs and other access methods

HTTP API
SPARQL 1.1

JDBC
ODBC

.NET Client API
HTTP API
LINQ

JDBC
ODBC

Supported programming languages

C++
Java
JavaScript (Node.js)
PHP
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Server-side scripts

Stored procedures

yes

SQLScript, R

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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, Role-Based Access Control (RBAC) supported

Role based authorization

yes

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.