DBMS > Dragonfly vs. Geode vs. SQLite vs. TinkerGraph

System Properties Comparison Dragonfly vs. Geode vs. SQLite vs. TinkerGraph

Please select another system to include it in the comparison.

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Widely used embeddable, in-process RDBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Key-value store

Relational DBMS

Graph DBMS

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

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

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.08
Rank	#345	Overall
	#34	Graph DBMS

Website

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

geode.apache.org

www.sqlite.org

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

www.dragonflydb.io/docs

geode.apache.org/docs

www.sqlite.org/docs.html

Developer

DragonflyDB team and community contributors

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Dwayne Richard Hipp

Initial release

2023

2002

2000

2009

Current release

1.0, March 2023

1.1, February 2017

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Public Domain

Open Source

Apache 2.0

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

C++

Java

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

server-less

Data scheme

scheme-free

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

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

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

TinkerPop 3

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

.Net
All JVM based languages
C++
Groovy
Java
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Groovy
Java

Server-side scripts

Stored procedures

Lua

user defined functions

Triggers

publish/subscribe channels provide some trigger functionality

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Atomic execution of command blocks and scripts

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

via file-system locks

Durability

Support for making data persistent

yes

optional

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 per client and object definable

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.