DBMS > AnzoGraph DB vs. Databricks vs. Datomic vs. Snowflake

System Properties Comparison AnzoGraph DB vs. Databricks vs. Datomic vs. Snowflake

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

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Primary database model

Graph DBMS
RDF store

Document store
Relational DBMS

Relational DBMS

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	84.24
Rank	#14	Overall
	#2	Document stores
	#9	Relational DBMS

Score	1.55
Rank	#144	Overall
	#67	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

cambridgesemantics.com/anzograph

www.databricks.com

www.datomic.com

www.snowflake.com

Technical documentation

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

docs.databricks.com

docs.datomic.com

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

Databricks

Cognitect

Snowflake Computing Inc.

Initial release

2018

2013

2012

2014

Current release

2.3, January 2021

1.0.7180, July 2024

License

Commercial or Open Source

commercial

free trial version available

commercial

limited edition free

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

Java, Clojure

Server operating systems

Linux

hosted

All OS with a Java VM

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

Flexible Schema (defined schema, partial schema, schema free)

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.

with Databricks SQL

yes

APIs and other access methods

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

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Python

Python
R
Scala

Clojure
Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

Transaction Functions

user defined functions

Triggers

By using transaction functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

But extensive use of caching in the application peers

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

yes

none

But extensive use of caching in the application peers

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

User concepts

Access control

Access rights for users and roles

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

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.