DBMS > Amazon Aurora vs. Datomic vs. Ehcache vs. OrigoDB vs. SQLite

System Properties Comparison Amazon Aurora vs. Datomic vs. Ehcache vs. OrigoDB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A widely adopted Java cache with tiered storage options

A fully ACID in-memory object graph database

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/rds/aurora

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.datomic.com

www.ehcache.org/documentation

origodb.com/docs

www.sqlite.org/docs.html

Developer

Amazon

Cognitect

Terracotta Inc, owned by Software AG

Robert Friberg et al

Dwayne Richard Hipp

Initial release

2015

2012

2009

under the name LiveDB

2000

Current release

1.0.7075, December 2023

3.10.0, March 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available

Open Source

Public Domain

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, Clojure

Java

Server operating systems

hosted

All OS with a Java VM

Linux
Windows

server-less

Data scheme

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

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.

yes

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP API

JCache

.NET Client API
HTTP API
LINQ

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java

Java

.Net

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

Transaction Functions

yes

Triggers

yes

By using transaction functions

yes

Cache Event Listeners

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

But extensive use of caching in the application peers

Sharding

by using Terracotta Server

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

But extensive use of caching in the application peers

yes

by using Terracotta Server

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)

Foreign keys

Referential integrity

yes

depending on model

yes

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

via file-system locks

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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

recommended only for testing and development

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.