DBMS > GeoMesa vs. KeyDB vs. OpenQM vs. RDFox

System Properties Comparison GeoMesa vs. KeyDB vs. OpenQM vs. RDFox

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

High performance knowledge graph and semantic reasoning engine

Primary database model

Secondary database models

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.29
Rank	#300	Overall
	#24	Graph DBMS
	#13	RDF stores

Website

www.geomesa.org

github.com/Snapchat/KeyDB
keydb.dev

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

www.oxfordsemantic.tech

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

docs.keydb.dev

docs.oxfordsemantic.tech

Developer

CCRi and others

EQ Alpha Technology Ltd.

Rocket Software, originally Martin Phillips

Oxford Semantic Technologies

Initial release

2014

2019

1993

2017

Current release

5.0.0, May 2024

3.4-12

6.0, Septermber 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD-3

Open Source

GPLv2, extended commercial license 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.

Implementation language

Scala

C++

Server operating systems

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

with some exceptions

yes

RDF schemas

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

RESTful HTTP API
SPARQL 1.1

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

.Net
Basic
C
Java
Objective C
PHP
Python

C
Java

Server-side scripts

Stored procedures

Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

yes

replication via a shared file system

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Immediate Consistency in stand-alone mode, Eventual Consistency in replicated setups

Foreign keys

Referential integrity

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control and ACL

Access rights can be defined down to the item level

Roles, resources, and access types

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

Use semantic reasoning to infer new facts from your RDF graph by integrating RDFox with Amazon Neptune | Amazon ...
20 February 2023, AWS Blog

The intuitions behind Knowledge Graphs and Reasoning | by Peter Crocker
5 May 2020, Towards Data Science

Eight interesting open-source graph databases
3 January 2023, INDIAai

Financial Crime Discovery using Amazon EKS and Graph Databases | Amazon Web Services
1 February 2022, AWS Blog

Top 9 Open Source Graph Databases – AIM
7 November 2022, Analytics India Magazine

provided by Google News

Share this page