DBMS > GeoMesa vs. KeyDB vs. Oracle NoSQL

System Properties Comparison GeoMesa vs. KeyDB vs. Oracle NoSQL

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Spatial DBMS

Key-value store

Document store
Key-value store
Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Website

www.geomesa.org

github.com/Snapchat/KeyDB
keydb.dev

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

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

docs.keydb.dev

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

CCRi and others

EQ Alpha Technology Ltd.

Oracle

Initial release

2014

2019

2011

Current release

4.0.5, February 2024

23.3, December 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD-3

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Java

Server operating systems

Linux

Linux
Solaris SPARC/x86

Data scheme

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

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

optional

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

by using the Redis Search module

yes

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

RESTful HTTP API

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

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency
Strong eventual consistency with CRDTs

Eventual Consistency
Immediate Consistency

depending on configuration

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

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control and ACL

Access rights for users and roles

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

Snap snaps up database developer KeyDB to make its infrastructure more snappy
12 May 2022, TechCrunch

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

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

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

Redis 6 arrives with multithreading for faster I/O
30 April 2020, InfoWorld

provided by Google News

Enhance enterprise data security and trust: Must see Blockchain Technology sessions at Oracle CloudWorld 2023
21 August 2023, Oracle

We built a geo-distributed, serverless modern app using the Oracle NoSQL Database Cloud Service
18 November 2021, Oracle

Oracle Beefs Up Its NoSQL Database Offering
3 April 2014, Data Center Knowledge

Oracle Defends Relational DBs Against NoSQL Competitors
25 November 2015, eWeek

Larry Ellison Just Embraced the Enemy. Or Did He?
1 October 2012, WIRED

provided by Google News

Share this page