DBMS > AnzoGraph DB vs. Dolt vs. Drizzle vs. Snowflake

System Properties Comparison AnzoGraph DB vs. Dolt vs. Drizzle vs. Snowflake

Please select another system to include it in the comparison.

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

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

A MySQL compatible DBMS with Git-like versioning of data and schema

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

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

Primary database model

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Document store

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

Score	0.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

cambridgesemantics.com/anzograph

github.com/dolthub/dolt
www.dolthub.com

www.snowflake.com

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

docs.dolthub.com

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

DoltHub Inc

Drizzle project, originally started by Brian Aker

Snowflake Computing Inc.

Initial release

2018

2008

2014

Current release

2.3, January 2021

7.2.4, September 2012

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache Version 2.0

Open Source

GNU GPL

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

Server operating systems

Linux

Linux
macOS
Windows

FreeBSD
Linux
OS X

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

yes

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

Typing

predefined data types such as float or date

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

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

with proprietary extensions

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

CLI Client
HTTP REST

JDBC

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Java
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

currently in alpha release

user defined functions

Triggers

yes

hooks for callbacks inside the server can be used.

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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 rights for users and roles

Only one user is configurable, and must be specified in the config file at startup

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.