DBMS > Geode vs. OpenQM vs. Qdrant vs. SpatiaLite vs. SQLite

System Properties Comparison Geode vs. OpenQM vs. Qdrant vs. SpatiaLite 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

QpenQM is a high-performance, self-tuning, multi-value DBMS

A high-performance vector database with neural network or semantic-based matching

Spatial extension of SQLite

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

geode.apache.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

github.com/qdrant/qdrant
qdrant.tech

www.gaia-gis.it/fossil/libspatialite/index

www.sqlite.org

Technical documentation

geode.apache.org/docs

qdrant.tech/documentation

www.gaia-gis.it/gaia-sins/spatialite_topics.html

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.

Rocket Software, originally Martin Phillips

Qdrant

Alessandro Furieri

Dwayne Richard Hipp

Initial release

2002

1993

2021

2008

2000

Current release

1.1, February 2017

3.4-12

5.0.0, August 2020

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPLv2, extended commercial license available

Open Source

Apache Version 2.0

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

Rust

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Docker
Linux
macOS
Windows

server-less

Data scheme

schema-free

yes

with some exceptions

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
Basic
C
Java
Objective C
PHP
Python

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

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

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Collection-level replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

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

User concepts

Access control

Access rights per client and object definable

Access rights can be defined down to the item level

Key-based authentication

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.