DBMS > EJDB vs. Snowflake vs. Tarantool vs. TimesTen

System Properties Comparison EJDB vs. Snowflake vs. Tarantool 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)

Cloud-based data warehousing service for structured and semi-structured data

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

In-Memory RDBMS compatible to Oracle

Primary database model

Document store

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

github.com/Softmotions/ejdb

www.snowflake.com

www.tarantool.io

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

Technical documentation

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

docs.snowflake.net/manuals/index.html

www.tarantool.io/en/doc

docs.oracle.com/database/timesten-18.1

Developer

Softmotions

Snowflake Computing Inc.

Oracle, TimesTen Performance Software, HP

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

Initial release

2012

2014

2008

1998

Current release

2.10.0, May 2022

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

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

C and C++

Server operating systems

server-less

hosted

BSD
Linux
macOS

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

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Full-featured ANSI SQL support

yes

APIs and other access methods

in-process shared library

CLI Client
JDBC
ODBC

Open binary protocol

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

JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

Lua, C and SQL stored procedures

PL/SQL

Triggers

similar concept for controling cloud resources

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

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, full featured in-memory storage engine with persistence

yes

User concepts

Access control

Users with fine-grained authorization concept, user roles and pluggable authentication

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.