DBMS > Amazon Redshift vs. Ehcache vs. mSQL vs. OrigoDB vs. Realm

System Properties Comparison Amazon Redshift vs. Ehcache vs. mSQL vs. OrigoDB vs. Realm

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted Java cache with tiered storage options

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Document store
Object oriented DBMS

Document store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	5.23
Rank	#68	Overall
	#8	Key-value stores

Score	1.67
Rank	#151	Overall
	#70	Relational DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	7.71
Rank	#52	Overall
	#9	Document stores

Website

aws.amazon.com/redshift

www.ehcache.org

hughestech.com.au/products/msql

origodb.com

realm.io

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

origodb.com/docs

realm.io/docs

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Hughes Technologies

Robert Friberg et al

Realm, acquired by MongoDB in May 2019

Initial release

2012

2009

1994

2009

under the name LiveDB

2014

Current release

3.10.0, March 2022

4.4, October 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

free licenses can be provided

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

Java

Server operating systems

hosted

All OS with a Java VM

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

Linux
Windows

Android
Backend: server-less
iOS
Windows

Data scheme

yes

schema-free

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

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

JCache

JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

Java

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

user defined functions

in Python

yes

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Cache Event Listeners

yes

Domain Events

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

depending on model

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

In-Memory realm

User concepts

Access control

fine grained access rights according to SQL-standard

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.