DBMS > Cachelot.io vs. GridGain vs. MySQL vs. SAP SQL Anywhere vs. SpaceTime

System Properties Comparison Cachelot.io vs. GridGain vs. MySQL vs. SAP SQL Anywhere vs. SpaceTime

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

GridGain is an in-memory computing platform, built on Apache Ignite

Widely used open source RDBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	0.04
Rank	#388	Overall
	#62	Key-value stores

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

cachelot.io

www.gridgain.com

www.mysql.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.mireo.com/spacetime

Technical documentation

www.gridgain.com/docs/index.html

dev.mysql.com/doc

help.sap.com/docs/SAP_SQL_Anywhere

Developer

GridGain Systems, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

SAP

formerly Sybase

Mireo

Initial release

2015

2007

1995

1992

2020

Current release

GridGain 8.5.1

8.4.0, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

Simplified BSD License

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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.

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

Implementation language

C++

Java, C++, .Net

C and C++

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux

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

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

yes

A subset of ANSI SQL is implemented

APIs and other access methods

Memcached protocol

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
HTTP API
JDBC
ODBC

RESTful HTTP API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
C++
Python

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

proprietary syntax

yes, in C/C++, Java, .Net or Perl

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

Security Hooks for custom implementations

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

yes

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.