DBMS > Geode vs. IBM Cloudant vs. Immudb vs. Kinetica vs. SQLite

System Properties Comparison Geode vs. IBM Cloudant vs. Immudb vs. Kinetica vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Database as a Service offering based on Apache CouchDB

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Fully vectorized database across both GPUs and CPUs

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

geode.apache.org

www.ibm.com/products/cloudant

github.com/codenotary/immudb
immudb.io

www.kinetica.com

www.sqlite.org

Technical documentation

geode.apache.org/docs

cloud.ibm.com/docs/Cloudant

docs.immudb.io

docs.kinetica.com

www.sqlite.org/docs.html

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Codenotary

Kinetica

Dwayne Richard Hipp

Initial release

2002

2010

2020

2012

2000

Current release

1.1, February 2017

1.2.3, April 2022

7.1, August 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Public Domain

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

Erlang

C, C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

BSD
Linux
macOS
Solaris
Windows
z/OS

Linux

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like syntax

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

gRPC protocol
PostgreSQL wire protocol

JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
Go
Java
JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

Cache Event Listeners

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

via file-system locks

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

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights per client and object definable

Access rights for users can be defined per database

Access rights for users and roles on table level

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.