DBMS > Ehcache vs. OrigoDB vs. Realm vs. Sequoiadb vs. SQLite

System Properties Comparison Ehcache vs. OrigoDB vs. Realm vs. Sequoiadb vs. SQLite

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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

NewSQL database with distributed OLTP and SQL

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Document store
Object oriented DBMS

Document store

Document store
Relational DBMS

Relational DBMS

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

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

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

www.ehcache.org/documentation

origodb.com/docs

realm.io/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

www.sqlite.org/docs.html

Developer

Terracotta Inc, owned by Software AG

Robert Friberg et al

Realm, acquired by MongoDB in May 2019

Sequoiadb Ltd.

Dwayne Richard Hipp

Initial release

2009

under the name LiveDB

2014

2013

2000

Current release

3.10.0, March 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Server: AGPL; Client: Apache V2

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

Linux
Windows

Android
Backend: server-less
iOS
Windows

Linux

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

oid, date, timestamp, binary, regex

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JCache

.NET Client API
HTTP API
LINQ

proprietary protocol using JSON

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

.Net

.Net
Java

with Android only
Objective-C
React Native
Swift

.Net
C++
Java
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

runs within the applications so server-side scripts are unnecessary

JavaScript

Triggers

yes

Cache Event Listeners

yes

Domain Events

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

horizontal partitioning

client side managed; servers are not synchronized

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Source-replica replication

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

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

yes

User concepts

Access control

Role based authorization

yes

simple password-based access control

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.