DBMS > Amazon Redshift vs. EJDB vs. mSQL vs. OpenQM vs. OrigoDB

System Properties Comparison Amazon Redshift vs. EJDB vs. mSQL vs. OpenQM vs. OrigoDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

A fully ACID in-memory object graph database

Primary database model

Document store
Object oriented DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

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

Website

aws.amazon.com/redshift

github.com/Softmotions/ejdb

hughestech.com.au/products/msql

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

origodb.com

Technical documentation

docs.aws.amazon.com/redshift

github.com/Softmotions/ejdb/blob/master/README.md

origodb.com/docs

Developer

Amazon (based on PostgreSQL)

Softmotions

Hughes Technologies

Rocket Software, originally Martin Phillips

Robert Friberg et al

Initial release

2012

1994

1993

2009

under the name LiveDB

Current release

4.4, October 2021

3.4-12

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

free licenses can be provided

Open Source

GPLv2, extended commercial license available

Open Source

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

Server operating systems

hosted

server-less

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

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

A subset of ANSI SQL is implemented

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

APIs and other access methods

JDBC
ODBC

in-process shared library

JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

typically not needed, however similar functionality with collection joins possible

depending on model

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Write ahead log

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Role based authorization

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.