DBMS > mSQL vs. OpenQM vs. Snowflake vs. TerminusDB vs. YDB

System Properties Comparison mSQL vs. OpenQM vs. Snowflake vs. TerminusDB vs. YDB

Editorial information provided by DB-Engines

Name

Description

mSQL (Mini SQL) is a simple and lightweight RDBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

Cloud-based data warehousing service for structured and semi-structured data

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

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Document store
Relational DBMS

Secondary database models

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.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

hughestech.com.au/products/msql

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.snowflake.com

terminusdb.com

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

ydb.tech/en/docs

Developer

Hughes Technologies

Rocket Software, originally Martin Phillips

Snowflake Computing Inc.

DataChemist Ltd.

Yandex

Initial release

1994

1993

2014

2018

2019

Current release

4.4, October 2021

3.4-12

11.0.0, January 2023

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

GPLv2, extended commercial license available

commercial

Open Source

GPL V3

Open Source

Apache 2.0; commercial license available

Cloud-based only

Only available as a cloud service

yes

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

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

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

hosted

Linux

Data scheme

yes

with some exceptions

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

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

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)

SQL-like query language (YQL)

APIs and other access methods

JDBC
ODBC

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript (Node.js)
Python

JavaScript
Python

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Journaling Streams

Active-passive shard replication

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

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

in-memory journaling

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Access rights can be defined down to the item level

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

Access rights defined for Yandex Cloud users

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.