DBMS > EventStoreDB vs. Tarantool vs. Transbase

System Properties Comparison EventStoreDB vs. Tarantool vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Event Store

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	1.14
Rank	#181	Overall
	#1	Event Stores

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

www.eventstore.com

www.tarantool.io

www.transaction.de/en/products/transbase.html

Technical documentation

developers.eventstore.com

www.tarantool.io/en/doc

www.transaction.de/en/products/transbase/features.html

Developer

Event Store Limited

Transaction Software GmbH

Initial release

2012

2008

1987

Current release

21.2, February 2021

2.10.0, May 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

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

commercial

free development license

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 and C++

Server operating systems

Linux
Windows

BSD
Linux
macOS

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

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

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.

Secondary indexes

yes

SQL

Support of SQL

Full-featured ANSI SQL support

yes

APIs and other access methods

Open binary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Lua, C and SQL stored procedures

yes

Triggers

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

yes

Partitioning methods

Methods for storing different data on different nodes

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

Replication methods

Methods for redundantly storing data on multiple nodes

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

yes

Concurrency

Support for concurrent manipulation of data

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes, write ahead logging

yes

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

User concepts

Access control

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.

Related products and services

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

More resources

DB-Engines blog posts

Data processing speed and reliability: in-memory synchronous replication
9 November 2021, Vladimir Perepelytsya, Tarantool (sponsor)

show all

Recent citations in the news

TaranHouse: New Big Data Warehouse Announced by Tarantool
4 April 2018, Newswire

In-Memory Showdown: Redis vs. Tarantool
1 September 2021, Хабр

Tarantool Announces New Enterprise Version With Enhanced Scaling and Monitoring Capabilities
18 May 2018, Newswire

Deploying Tarantool Cartridge applications with zero effort (Part 1)
16 December 2019, Хабр

Deploying Tarantool Cartridge applications with zero effort (Part 2)
13 April 2020, Хабр

provided by Google News

Share this page