DBMS > Dragonfly vs. FatDB vs. JanusGraph vs. SpatiaLite

System Properties Comparison Dragonfly vs. FatDB vs. JanusGraph vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the 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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Spatial extension of SQLite

Primary database model

Key-value store

Document store
Key-value store

Graph DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

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

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

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

janusgraph.org

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

www.dragonflydb.io/docs

docs.janusgraph.org

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

DragonflyDB team and community contributors

FatCloud

Linux Foundation; originally developed as Titan by Aurelius

Alessandro Furieri

Initial release

2023

2012

2017

2008

Current release

1.0, March 2023

0.6.3, February 2023

5.0.0, August 2020

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

Open Source

Apache 2.0

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

C++

Server operating systems

Linux

Windows

Linux
OS X
Unix
Windows

server-less

Data scheme

scheme-free

schema-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.

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

Clojure
Java
Python

Server-side scripts

Stored procedures

Lua

yes

via applications

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

Can implement custom security layer via applications

User authentification and security via Rexster Graph Server

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

DragonflyDB Announces $21m in New Funding and General Availability
21 March 2023, Business Wire

DragonflyDB reels in $21M for its speedy in-memory database
21 March 2023, SiliconANGLE News

DragonflyDB Raises $21M in Funding
21 March 2023, FinSMEs

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Intel Linux Kernel Optimizations Show Huge Benefit For High Core Count Servers
29 March 2023, Phoronix

provided by Google News

Database Deep Dives: JanusGraph
8 August 2019, IBM

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex
30 July 2020, Towards Data Science

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

The year of the graph: Getting graphic, going native, reshaping the landscape
8 January 2018, ZDNet

provided by Google News

Share this page