DBMS > Ehcache vs. JaguarDB vs. Transbase vs. Vitess

System Properties Comparison Ehcache vs. JaguarDB vs. Transbase vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Performant, highly scalable DBMS for AI and IoT applications

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Key-value store

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.ehcache.org

www.jaguardb.com

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

vitess.io

Technical documentation

www.ehcache.org/documentation

www.jaguardb.com/support.html

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

vitess.io/docs

Developer

Terracotta Inc, owned by Software AG

DataJaguar, Inc.

Transaction Software GmbH

The Linux Foundation, PlanetScale

Initial release

2009

2015

1987

2013

Current release

3.10.0, March 2022

3.3 July 2023

Transbase 8.3, 2022

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL V3.0

commercial

free development license

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

Java

C++

the server part. Clients available in other languages

C and C++

Server operating systems

All OS with a Java VM

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

JCache

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

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

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication

Source-replica replication

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

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

Immediate Consistency

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

yes

supports JTA and can work as an XA resource

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

User concepts

Access control

rights management via user accounts

fine grained access rights according to SQL-standard

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

Recent citations in the news

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, dzone.com

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

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

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

provided by Google News

Share this page