DBMS > Dragonfly vs. Postgres-XL vs. RocksDB vs. ScyllaDB

System Properties Comparison Dragonfly vs. Postgres-XL vs. RocksDB vs. ScyllaDB

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Cassandra and DynamoDB compatible wide column store

Primary database model

Secondary database models

Document store
Spatial DBMS

Key-value store

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

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

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	4.08
Rank	#76	Overall
	#5	Wide column stores

Website

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

www.postgres-xl.org

rocksdb.org

www.scylladb.com

Technical documentation

www.dragonflydb.io/docs

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

docs.scylladb.com

Developer

DragonflyDB team and community contributors

Facebook, Inc.

ScyllaDB

Initial release

2023

2014

since 2012, originally named StormDB

2013

2015

Current release

1.0, March 2023

10 R1, October 2018

9.2.1, May 2024

ScyllaDB Open Source 5.4.1, January 2024

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Mozilla public license

Open Source

BSD

Open Source

Open Source (AGPL), commercial license available

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

C++

Server operating systems

Linux

Linux
macOS

Linux

Data scheme

scheme-free

yes

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

cluster global secondary indices

SQL

Support of SQL

yes

distributed, parallel query execution

SQL-like DML and DDL statements (CQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

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
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

Server-side scripts

Stored procedures

Lua

user defined functions

yes, Lua

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

selectable replication factor

Representation of geographical distribution of servers is possible

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
Tunable Consistency

can be individually decided for each write operation

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

MVCC

yes

Atomicity and isolation are supported for single operations

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

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

in-memory tables

User concepts

Access control

Password-based authentication

fine grained access rights according to SQL-standard

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» 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.