DBMS > Dragonfly vs. GeoMesa vs. RDF4J vs. Snowflake vs. VelocityDB

System Properties Comparison Dragonfly vs. GeoMesa vs. RDF4J vs. Snowflake vs. VelocityDB

Editorial information provided by DB-Engines

Name

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

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Cloud-based data warehousing service for structured and semi-structured data

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS
Object oriented DBMS

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

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

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

Technical documentation

www.dragonflydb.io/docs

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

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

velocitydb.com/UserGuide

Developer

DragonflyDB team and community contributors

CCRi and others

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

VelocityDB Inc

Initial release

2023

2014

2004

2014

2011

Current release

1.0, March 2023

5.0.0, May 2024

7.x

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache License 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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

Scala

Java

Server operating systems

Linux

Linux
OS X
Unix
Windows

hosted

Any that supports .NET

Data scheme

scheme-free

yes

RDF Schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

SQL

Support of SQL

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

.Net

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
PHP
Python

JavaScript (Node.js)
Python

.Net

Server-side scripts

Stored procedures

Lua

yes

user defined functions

Triggers

publish/subscribe channels provide some trigger functionality

yes

similar concept for controling cloud resources

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

depending on storage layer

Immediate Consistency

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

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

depending on storage layer

yes

User concepts

Access control

Password-based authentication

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept, user roles and pluggable authentication

Based on Windows Authentication

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.