DBMS > Tarantool vs. Vitess

System Properties Comparison Tarantool vs. Vitess

Please select another system to include it in the comparison.

Our visitors often compare Tarantool and Vitess with PostgreSQL, YDB and MongoDB.

Editorial information provided by DB-Engines

Name

Description

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

Document store
Spatial DBMS

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

Score	1.38
Rank	#152	Overall
	#26	Document stores
	#25	Key-value stores
	#68	Relational DBMS

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

Website

www.tarantool.io

vitess.io

Technical documentation

www.tarantool.io/en/doc

vitess.io/docs

Developer

The Linux Foundation, PlanetScale

Initial release

2008

2013

Current release

2.10.0, May 2022

15.0.2, December 2022

License

Commercial or Open Source

Open Source

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

Open Source

Apache Version 2.0, commercial licenses available

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

BSD
Linux
macOS

Docker
Linux
macOS

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

with proprietary extensions

APIs and other access methods

Open binary protocol

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Lua, C and SQL stored procedures

yes

proprietary syntax

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.

Sharding

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)

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

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes, cooperative multitasking

yes

table locks or row locks depending on storage engine

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

yes

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

Users with fine-grained authorization concept

no user groups or roles

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

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

Accelerating PHP connectors for Tarantool using Async, Swoole, and Parallel
18 December 2019, Хабр

VShard — horizontal scaling in Tarantool
7 March 2019, Хабр

provided by Google News

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

Update CNCF’s Vitess Scales MySQL with the Help of Kubernetes
29 March 2022, InApps Technology

PlanetScale Announces Developer-First, Instantly-Provisioned and Infinitely-Scalable Database for Companies of All Sizes
18 May 2021, Business Wire

PlanetScale review: Horizontally scalable MySQL in the cloud
1 September 2021, InfoWorld

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Share this page