DBMS > Citus vs. Geode vs. Hazelcast vs. Quasardb vs. SQLite

System Properties Comparison Citus vs. Geode vs. Hazelcast vs. Quasardb vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

A widely adopted in-memory data grid

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

docs.citusdata.com

geode.apache.org/docs

hazelcast.org/imdg/docs

doc.quasar.ai/master

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.

Hazelcast

quasardb

Dwayne Richard Hipp

Initial release

2010

2002

2008

2009

2000

Current release

8.1, December 2018

1.1, February 2017

5.3.6, November 2023

3.14.1, January 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2; commercial licenses available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Public Domain

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++

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java VM

BSD
Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

integer and binary

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.

yes

specific XML type available, but no XML query functionality

yes

the object must implement a serialization strategy

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

yes

standard, with numerous extensions

SQL-like query language (OQL)

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java Client API
Memcached protocol
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

yes

Event Listeners, Executor Services

Triggers

yes

Cache Event Listeners

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication

yes

Replicated Map

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

Role-based access control

Cryptographically strong user authentication and audit trail

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.