DBMS > Ehcache vs. GigaSpaces vs. Google BigQuery vs. Sphinx vs. Tarantool

System Properties Comparison Ehcache vs. GigaSpaces vs. Google BigQuery vs. Sphinx vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Large scale data warehouse service with append-only tables

Open source search engine for searching in data from different sources, e.g. relational databases

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

Primary database model

Key-value store

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Search engine

Document store
Key-value store
Relational DBMS

Secondary database models

Graph DBMS
Search engine

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

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

Website

www.ehcache.org

www.gigaspaces.com

cloud.google.com/bigquery

sphinxsearch.com

www.tarantool.io

Technical documentation

www.ehcache.org/documentation

docs.gigaspaces.com/latest/landing.html

cloud.google.com/bigquery/docs

sphinxsearch.com/docs

www.tarantool.io/en/doc

Developer

Terracotta Inc, owned by Software AG

Gigaspaces Technologies

Google

Sphinx Technologies Inc.

Initial release

2009

2000

2010

2001

2008

Current release

3.10.0, March 2022

15.5, September 2020

3.5.1, February 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2; Commercial licenses available

commercial

Open Source

GPL version 2, commercial licence available

Open Source

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

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

Java

Java, C++, .Net

C++

C and C++

Server operating systems

All OS with a Java VM

Linux
macOS
Solaris
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

yes

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

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.

XML can be used for describing objects metadata

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-99 for query and DML statements

yes

SQL-like query language (SphinxQL)

Full-featured ANSI SQL support

APIs and other access methods

JCache

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

RESTful HTTP/JSON API

Proprietary protocol

Open binary protocol

Supported programming languages

Java

.Net
C++
Java
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Lua, C and SQL stored procedures

Triggers

yes

Cache Event Listeners

yes, event driven architecture

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

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

yes

by using Terracotta Server

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

none

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Since BigQuery is designed for querying data

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

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

The original contents of fields are not stored in the Sphinx index.

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Role-based access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

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.