DBMS > Drizzle vs. HarperDB vs. JanusGraph vs. Kinetica vs. Snowflake

System Properties Comparison Drizzle vs. HarperDB vs. JanusGraph vs. Kinetica vs. Snowflake

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

docs.harperdb.io/docs

docs.janusgraph.org

docs.kinetica.com

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

HarperDB

Linux Foundation; originally developed as Titan by Aurelius

Kinetica

Snowflake Computing Inc.

Initial release

2008

2017

2012

2014

Current release

7.2.4, September 2012

3.1, August 2021

0.6.3, February 2023

7.1, August 2021

License

Commercial or Open Source

Open Source

GNU GPL

commercial

free community edition available

Open Source

Apache 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

C++

Node.js

Java

C, C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X

Linux
OS X
Unix
Windows

Linux

hosted

Data scheme

yes

dynamic schema

yes

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

Typing

predefined data types such as float or date

yes

JSON data types

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

with proprietary extensions

SQL-like data manipulation statements

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Clojure
Java
Python

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

yes

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

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

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

the nodes on which a table resides can be defined

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users and roles

User authentification and security via Rexster Graph Server

Access rights for users and roles on table level

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.