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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

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

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Graph DBMS
RDF store

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Document store

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

Score	0.22
Rank	#302	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.05
Rank	#359	Overall
	#50	Document stores
	#52	Key-value stores
	#23	Search engines
	#37	Time Series DBMS

Website

cambridgesemantics.com/anzograph

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

www.snowflake.com

www.tigrisdata.com

Technical documentation

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

docs.dolthub.com

docs.snowflake.net/manuals/index.html

www.tigrisdata.com/docs

Developer

Cambridge Semantics

DoltHub Inc

Snowflake Computing Inc.

Tigris Data, Inc.

Initial release

2018

2014

2022

Current release

2.3, January 2021

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2.0

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

Server operating systems

Linux

Linux
macOS
Windows

hosted

Linux
macOS
Windows

Data scheme

Schema-free and OWL/RDFS-schema support

yes

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

yes

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

APIs and other access methods

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

CLI Client
HTTP REST

CLI Client
JDBC
ODBC

CLI Client
gRPC
RESTful HTTP API

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

JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

currently in alpha release

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

yes

Sharding

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.

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

yes, using FoundationDB

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

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

Access rights for users and roles

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.