DBMS > EJDB vs. Quasardb vs. SQLite vs. TimesTen vs. VoltDB

System Properties Comparison EJDB vs. Quasardb vs. SQLite vs. TimesTen vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

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

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

In-Memory RDBMS compatible to Oracle

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store

Time Series DBMS

Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

github.com/Softmotions/ejdb

quasar.ai

www.sqlite.org

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

www.voltdb.com

Technical documentation

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

doc.quasar.ai/master

www.sqlite.org/docs.html

docs.oracle.com/database/timesten-18.1

docs.voltdb.com

Developer

Softmotions

quasardb

Dwayne Richard Hipp

Oracle, TimesTen Performance Software, HP

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

VoltDB Inc.

Initial release

2012

2009

2000

1998

2010

Current release

3.14.1, January 2024

3.45.3 (15 April 2024), April 2024

11 Release 2 (11.2.2.8.0)

11.3, April 2022

License

Commercial or Open Source

Open Source

GPLv2

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Public Domain

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++

Java, C++

Server operating systems

server-less

BSD
Linux
OS X
Windows

server-less

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

Linux
OS X

for development

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

integer and binary

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

yes

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

in-process shared library

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

PL/SQL

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication with selectable replication factor

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

by using LevelDB

yes

by means of logfiles and checkpoints

yes

Snapshots and command logging

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

Cryptographically strong user authentication and audit trail

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.