DBMS > Datomic vs. GeoSpock vs. KeyDB vs. PostGIS vs. RocksDB

System Properties Comparison Datomic vs. GeoSpock vs. KeyDB vs. PostGIS vs. RocksDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Spatial and temporal data processing engine for extreme data scale

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

Spatial extension of PostgreSQL

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

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

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.datomic.com

geospock.com

github.com/Snapchat/KeyDB
keydb.dev

postgis.net

rocksdb.org

Technical documentation

docs.datomic.com

docs.keydb.dev

postgis.net/documentation

github.com/facebook/rocksdb/wiki

Developer

Cognitect

GeoSpock

EQ Alpha Technology Ltd.

Facebook, Inc.

Initial release

2012

2019

2005

2013

Current release

1.0.7075, December 2023

2.0, September 2019

3.4.2, February 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

BSD-3

Open Source

GPL v2.0

Open Source

BSD

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, Clojure

Java, Javascript

C++

Server operating systems

All OS with a Java VM

hosted

Linux

Data scheme

yes

schema-free

yes

schema-free

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

temporal, categorical

yes

by using the Redis Search module

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

RESTful HTTP API

JDBC

Proprietary protocol

RESP - REdis Serialization Protoco

C++ API
Java API

Supported programming languages

Clojure
Java

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
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

Lua

user defined functions

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Automatic sharding

Sharding

yes

based on PostgreSQL

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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.

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users can be defined per table

simple password-based access control and ACL

yes

based on PostgreSQL

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.