DBMS > Apache Phoenix vs. Cubrid vs. Dragonfly vs. Snowflake

System Properties Comparison Apache Phoenix vs. Cubrid vs. Dragonfly vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

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.97
Rank	#126	Overall
	#59	Relational DBMS

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

phoenix.apache.org

cubrid.com (korean)
cubrid.org (english)

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

www.snowflake.com

Technical documentation

phoenix.apache.org

cubrid.org/manuals

www.dragonflydb.io/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

CUBRID Corporation, CUBRID Foundation

DragonflyDB team and community contributors

Snowflake Computing Inc.

Initial release

2014

2008

2023

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

11.0, January 2021

1.0, March 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

BSL 1.1

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

C++

Server operating systems

Linux
Unix
Windows

Linux
Windows

Linux

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

yes

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

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
OLE DB

Proprietary protocol

RESP - REdis Serialization Protocol

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

Lua

user defined functions

Triggers

yes

publish/subscribe channels provide some trigger functionality

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

fine grained access rights according to SQL-standard

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.