DBMS > Dragonfly vs. Kinetica vs. Snowflake vs. TerminusDB

System Properties Comparison Dragonfly vs. Kinetica vs. Snowflake vs. TerminusDB

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

Fully vectorized database across both GPUs and CPUs

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Key-value store

Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
RDF store

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

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

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

www.kinetica.com

www.snowflake.com

terminusdb.com

Technical documentation

www.dragonflydb.io/docs

docs.kinetica.com

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

DragonflyDB team and community contributors

Kinetica

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

2023

2012

2014

2018

Current release

1.0, March 2023

7.1, August 2021

11.0.0, January 2023

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux

hosted

Linux

Data scheme

scheme-free

yes

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

yes

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language (WOQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

Lua

user defined functions

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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, strict serializability by the server

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

GPU vRAM or System RAM

User concepts

Access control

Password-based authentication

Access rights for users and roles on table level

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.