DBMS > Apache Kylin vs. Dragonfly vs. etcd vs. Snowflake

System Properties Comparison Apache Kylin vs. Dragonfly vs. etcd vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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 distributed reliable key-value store

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

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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

Score	1.18
Rank	#172	Overall
	#79	Relational DBMS

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

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

kylin.apache.org

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

etcd.io
github.com/etcd-io/etcd

www.snowflake.com

Technical documentation

kylin.apache.org/docs

www.dragonflydb.io/docs

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation, originally contributed from eBay Inc

DragonflyDB team and community contributors

Snowflake Computing Inc.

Initial release

2015

2023

2014

Current release

3.1.0, July 2020

1.0, March 2023

3.4, August 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSL 1.1

Open Source

Apache Version 2.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

Java

C++

Server operating systems

Linux

FreeBSD
Linux
Windows

experimental

hosted

Data scheme

yes

scheme-free

schema-free

yes

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

Typing

predefined data types such as float or date

yes

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

ANSI SQL for queries (using Apache Calcite)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protocol

gRPC
JSON over HTTP

CLI Client
JDBC
ODBC

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++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

user defined functions

Triggers

publish/subscribe channels provide some trigger functionality

yes, watching key changes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

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

User concepts

Access control

Password-based authentication

Users with fine-grained authorization concept, user roles and pluggable 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.