DBMS > Ehcache vs. GigaSpaces vs. Kyligence Enterprise vs. PostGIS vs. RocksDB

System Properties Comparison Ehcache vs. GigaSpaces vs. Kyligence Enterprise vs. PostGIS vs. RocksDB

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

A distributed analytics engine for big data, built on top of Apache Kylin

Spatial extension of PostgreSQL

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Spatial DBMS

Key-value store

Secondary database models

Graph DBMS
Search engine

Relational DBMS

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	0.46
Rank	#266	Overall
	#124	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.ehcache.org

www.gigaspaces.com

kyligence.io/kyligence-enterprise

postgis.net

rocksdb.org

Technical documentation

www.ehcache.org/documentation

docs.gigaspaces.com/latest/landing.html

postgis.net/documentation

github.com/facebook/rocksdb/wiki

Developer

Terracotta Inc, owned by Software AG

Gigaspaces Technologies

Kyligence, Inc.

Facebook, Inc.

Initial release

2009

2000

2016

2005

2013

Current release

3.10.0, March 2022

15.5, September 2020

3.4.2, February 2024

9.2.1, May 2024

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 v2.0

Open Source

BSD

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

Java, C++, .Net

Java

C++

Server operating systems

All OS with a Java VM

Linux
macOS
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-free

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

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

JCache

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

JDBC
ODBC
RESTful HTTP API

C++ API
Java API

Supported programming languages

Java

.Net
C++
Java
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

yes

based on PostgreSQL

horizontal partitioning

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

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

yes

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

yes

Concurrency

Support for concurrent manipulation of data

yes

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

Role-based access control

yes

based on PostgreSQL

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.