DBMS > Dragonfly vs. GeoSpock vs. MySQL vs. TerminusDB

System Properties Comparison Dragonfly vs. GeoSpock vs. MySQL vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Spatial and temporal data processing engine for extreme data scale

Widely used open source RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

Document store
RDF store

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

Score	0.44
Rank	#255	Overall
	#38	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

github.com/dragonflydb/dragonfly
www.dragonflydb.io

geospock.com

www.mysql.com

terminusdb.com

Technical documentation

www.dragonflydb.io/docs

dev.mysql.com/doc

terminusdb.github.io/terminusdb/#

Developer

DragonflyDB team and community contributors

GeoSpock

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Initial release

2023

1995

2018

Current release

1.0, March 2023

2.0, September 2019

9.0.0, July 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

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

C++

Java, Javascript

C and C++

Prolog, Rust

Server operating systems

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

scheme-free

yes

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript
Python

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

Password-based authentication

Access rights for users can be defined per table

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

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.