DBMS > EJDB vs. Riak KV vs. SQLite vs. TimesTen

System Properties Comparison EJDB vs. Riak KV vs. SQLite vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed, fault tolerant key-value store

Widely used embeddable, in-process RDBMS

In-Memory RDBMS compatible to Oracle

Primary database model

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

github.com/Softmotions/ejdb

www.sqlite.org

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

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

www.tiot.jp/riak-docs/riak/kv/latest

www.sqlite.org/docs.html

docs.oracle.com/database/timesten-18.1

Developer

Softmotions

OpenSource, formerly Basho Technologies

Dwayne Richard Hipp

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

2009

2000

1998

Current release

3.2.0, December 2022

3.46.0 (23 May 2024), May 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache version 2, commercial enterprise edition

Open Source

Public Domain

commercial

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

Erlang

Server operating systems

server-less

Linux
OS X

server-less

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

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

APIs and other access methods

in-process shared library

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

Erlang

PL/SQL

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

links between data sets can be stored

yes

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

via file-system locks

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

yes, using Riak Security

fine grained access rights according to SQL-standard

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.