DBMS > Ehcache vs. GigaSpaces vs. Google BigQuery vs. Lovefield

System Properties Comparison Ehcache vs. GigaSpaces vs. Google BigQuery vs. Lovefield

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

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

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Key-value store

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Secondary database models

Graph DBMS
Search engine

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	0.29
Rank	#293	Overall
	#133	Relational DBMS

Website

www.ehcache.org

www.gigaspaces.com

cloud.google.com/bigquery

google.github.io/lovefield

Technical documentation

www.ehcache.org/documentation

docs.gigaspaces.com/latest/landing.html

cloud.google.com/bigquery/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Terracotta Inc, owned by Software AG

Gigaspaces Technologies

Google

Initial release

2009

2000

2010

2014

Current release

3.10.0, March 2022

15.5, September 2020

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2; Commercial licenses available

commercial

Open Source

Apache 2.0

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

JavaScript

Server operating systems

All OS with a Java VM

Linux
macOS
Solaris
Windows

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

yes

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

JCache

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

RESTful HTTP/JSON API

Supported programming languages

Java

.Net
C++
Java
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Triggers

yes

Cache Event Listeners

yes, event driven architecture

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

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

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

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

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

yes

using MemoryDB

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)

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.