DBMS > EJDB vs. FatDB vs. TimesTen vs. VoltDB

System Properties Comparison EJDB vs. FatDB vs. TimesTen vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Document store
Key-value store

Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

github.com/Softmotions/ejdb

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

www.voltdb.com

Technical documentation

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

docs.oracle.com/database/timesten-18.1

docs.voltdb.com

Developer

Softmotions

FatCloud

Oracle, TimesTen Performance Software, HP

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

VoltDB Inc.

Initial release

2012

1998

2010

Current release

11 Release 2 (11.2.2.8.0)

11.3, April 2022

License

Commercial or Open Source

Open Source

GPLv2

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

Java, C++

Server operating systems

server-less

Windows

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

Linux
OS X

for development

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

Via inetgration in SQL Server

yes

only a subset of SQL 99

APIs and other access methods

in-process shared library

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

C
C++
Java
PL/SQL

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

PL/SQL

Java

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

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

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

Data access is serialized by the server

Durability

Support for making data persistent

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

User concepts

Access control

Can implement custom security layer via applications

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

The Intel Xeon E7-8800 v3 Review: The POWER8 Killer?
8 May 2015, AnandTech

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page