DBMS > Dragonfly vs. InfluxDB vs. OrigoDB vs. RocksDB

System Properties Comparison Dragonfly vs. InfluxDB vs. OrigoDB vs. RocksDB

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

DBMS for storing time series, events and metrics

A fully ACID in-memory object graph database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store

Time Series DBMS

Document store
Object oriented DBMS

Key-value store

Secondary database models

Spatial DBMS

with GEO package

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

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

Score	25.83
Rank	#28	Overall
	#1	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

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

www.influxdata.com/products/influxdb-overview

origodb.com

rocksdb.org

Technical documentation

www.dragonflydb.io/docs

docs.influxdata.com/influxdb

origodb.com/docs

github.com/facebook/rocksdb/wiki

Developer

DragonflyDB team and community contributors

Robert Friberg et al

Facebook, Inc.

Initial release

2023

2013

2009

under the name LiveDB

2013

Current release

1.0, March 2023

2.7.6, April 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

MIT-License; commercial enterprise version available

Open Source

BSD

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

Server operating systems

Linux

Linux
OS X

through Homebrew

Linux
Windows

Linux

Data scheme

scheme-free

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

Numeric data and Strings

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

HTTP API
JSON over UDP

.NET Client API
HTTP API
LINQ

C++ API
Java 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

.Net
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Perl
PHP
Python
R
Ruby
Rust
Scala

.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Lua

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

in enterprise version only

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

in enterprise version only

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

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

yes

Depending on used storage engine

yes

User concepts

Access control

Password-based authentication

simple rights management via user accounts

Role based authorization

More information provided by the system vendor

Specific characteristics

InfluxData is the creator of InfluxDB , the open source time series database. It...
» more

Competitive advantages

Time to Value InfluxDB is available in all the popular languages and frameworks,...
» more

Typical application scenarios

IoT & Sensor Monitoring Developers are witnessing the instrumentation of every available...
» more

Key customers

InfluxData has more than 1,900 paying customers, including customers include MuleSoft,...
» more

Market metrics

Fastest-growing database to drive 27,500 GitHub stars Over 750,000 daily active instances
» more

Licensing and pricing models

Open source core with closed source clustering available either on-premise or on...
» more

News

Using Parquet’s Bloom Filters
28 May 2024

Efficiency Unleashed: Streamlining Workflows with the InfluxDB Management API
23 May 2024

What is DevRel at InfluxData
21 May 2024

An Introductory Guide to Grafana Alerts
16 May 2024

What to Expect When You’re Expecting InfluxDB: A Guide
14 May 2024

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.