DBMS > Ehcache vs. GeoSpock vs. Infobright vs. MySQL

System Properties Comparison Ehcache vs. GeoSpock vs. Infobright vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

A widely adopted Java cache with tiered storage options

Spatial and temporal data processing engine for extreme data scale

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Widely used open source RDBMS

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Time Series DBMS

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.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.ehcache.org

geospock.com

ignitetech.com/softwarelibrary/infobrightdb

www.mysql.com

Technical documentation

www.ehcache.org/documentation

dev.mysql.com/doc

Developer

Terracotta Inc, owned by Software AG

GeoSpock

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2009

2005

1995

Current release

3.10.0, March 2022

2.0, September 2019

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

Java, Javascript

C and C++

Server operating systems

All OS with a Java VM

hosted

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

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.

yes

Secondary indexes

temporal, categorical

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

APIs and other access methods

JCache

JDBC

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Automatic sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

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)

Immediate Consistency

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

ACID

not for MyISAM storage engine

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

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.