DBMS > Cubrid vs. Dragonfly vs. EJDB vs. Snowflake

System Properties Comparison Cubrid vs. Dragonfly vs. EJDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Primary database model

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

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

github.com/Softmotions/ejdb

www.snowflake.com

Technical documentation

cubrid.org/manuals

www.dragonflydb.io/docs

github.com/Softmotions/ejdb/blob/master/README.md

docs.snowflake.net/manuals/index.html

Developer

CUBRID Corporation, CUBRID Foundation

DragonflyDB team and community contributors

Softmotions

Snowflake Computing Inc.

Initial release

2008

2023

2012

2014

Current release

11.0, January 2021

1.0, March 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSL 1.1

Open Source

GPLv2

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

C, C++, Java

C++

Server operating systems

Linux
Windows

Linux

server-less

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

string, integer, double, bool, date, object_id

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

ADO.NET
JDBC
ODBC
OLE DB

Proprietary protocol

RESP - REdis Serialization Protocol

in-process shared library

CLI Client
JDBC
ODBC

Supported programming languages

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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

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.