DBMS > AnzoGraph DB vs. Coveo vs. JanusGraph vs. Snowflake

System Properties Comparison AnzoGraph DB vs. Coveo vs. JanusGraph 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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

A Graph DBMS optimized for distributed clusters

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

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

Primary database model

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	2.11
Rank	#118	Overall
	#11	Search engines

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

cambridgesemantics.com/anzograph

www.coveo.com

janusgraph.org

www.snowflake.com

Technical documentation

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

docs.coveo.com

docs.janusgraph.org

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

Coveo

Linux Foundation; originally developed as Titan by Aurelius

Snowflake Computing Inc.

Initial release

2018

2012

2017

2014

Current release

2.3, January 2021

0.6.3, February 2023

License

Commercial or Open Source

commercial

free trial version available

commercial

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

Java

Server operating systems

Linux

hosted

Linux
OS X
Unix
Windows

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

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

APIs and other access methods

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

RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Python

C#
Java
JavaScript
Python

Clojure
Java
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

yes

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

User concepts

Access control

Access rights for users and roles

granular access controls, API key management, content filters

User authentification and security via Rexster Graph Server

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.