DBMS > GridGain vs. KairosDB vs. MySQL vs. ObjectBox

System Properties Comparison GridGain vs. KairosDB vs. MySQL vs. ObjectBox

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed Time Series DBMS based on Cassandra or H2

Widely used open source RDBMS

Lightweight, fast on-device database for IoT, Mobile and Embedded devices, persisting and synchronising objects and vectors

Primary database model

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Object oriented DBMS
Vector DBMS

Secondary database models

Document store
Spatial DBMS

Time Series DBMS

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

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.08
Rank	#179	Overall
	#6	Object oriented DBMS
	#9	Vector DBMS

Website

www.gridgain.com

github.com/kairosdb/kairosdb

www.mysql.com

github.com/objectbox
objectbox.io

Technical documentation

www.gridgain.com/docs/index.html

kairosdb.github.io

dev.mysql.com/doc

docs.objectbox.io

Developer

GridGain Systems, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

ObjectBox Limited

Initial release

2007

2013

1995

2017

Current release

GridGain 8.5.1

1.2.2, November 2018

9.0.0, July 2024

4.0 (May 2024)

License

Commercial or Open Source

commercial, open source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Bindings are released under Apache 2.0

Apache License 2.0

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, C++, .Net, Python, REST, SQL

Java

C and C++

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, plus "flex" map-like types

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

APIs and other access methods

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

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary native API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Java
JavaScript

Node.js
PHP
Python

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

C
C++
Dart (Flutter)
Go
Java
Kotlin
Python
Swift

Server-side scripts

Stored procedures

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

yes

proprietary syntax

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

Data sync between devices allowing occasional connected databases to work completely offline

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

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

Role-based access control
Security Hooks for custom implementations

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

yes

More information provided by the system vendor

News

MongoDB Realm & Device Sync alternatives – ObjectBox
17 September 2024

Local AI – what it is and why we need it
11 September 2024

First on-device Vector Database (aka Semantic Index) for iOS
24 July 2024

Retrieval Augmented Generation (RAG) with vector databases: Expanding AI Capabilities
18 June 2024

The on-device Vector Database for Android and Java
29 May 2024

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.