DBMS > Dragonfly vs. GeoSpock vs. H2GIS vs. OpenSearch

System Properties Comparison Dragonfly vs. GeoSpock vs. H2GIS vs. OpenSearch

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

Spatial extension of H2

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Secondary database models

Time Series DBMS

Relational DBMS

Vector DBMS

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

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

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

geospock.com

www.h2gis.org

github.com/opensearch-project
opensearch.org

Technical documentation

www.dragonflydb.io/docs

www.h2gis.org/docs/home

opensearch.org/docs/latest

Developer

DragonflyDB team and community contributors

GeoSpock

CNRS

Amazon Web Services

Initial release

2023

2013

2021

Current release

1.0, March 2023

2.0, September 2019

2.5.0, January 2023

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

Open Source

LGPL 3.0

Open Source

Apache Version 2.0

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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

C++

Java, Javascript

Java

Server operating systems

Linux

hosted

All OS with a Java VM

Data scheme

scheme-free

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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.

Secondary indexes

temporal, categorical

yes

All search fields are automatically indexed

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like query language

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

JDBC

Java API
RESTful HTTP/JSON API

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

Java

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

Lua

yes

based on H2

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

based on H2

yes

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

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

yes, multi-version concurrency control (MVCC)

yes

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

Password-based authentication

Access rights for users can be defined per table

yes

based on H2

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.