DBMS > AnzoGraph DB vs. IBM Cloudant vs. Qdrant vs. Snowflake

System Properties Comparison AnzoGraph DB vs. IBM Cloudant vs. Qdrant 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

Database as a Service offering based on Apache CouchDB

A high-performance vector database with neural network or semantic-based matching

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.22
Rank	#302	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

cambridgesemantics.com/anzograph

www.ibm.com/products/cloudant

github.com/qdrant/qdrant
qdrant.tech

www.snowflake.com

Technical documentation

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

cloud.ibm.com/docs/Cloudant

qdrant.tech/documentation

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Qdrant

Snowflake Computing Inc.

Initial release

2018

2010

2021

2014

Current release

2.3, January 2021

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

Apache Version 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

Erlang

Rust

Server operating systems

Linux

hosted

Docker
Linux
macOS
Windows

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

schema-free

yes

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

Typing

predefined data types such as float or date

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

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/JSON API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Multi-source replication
Source-replica replication

Collection-level replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Eventual Consistency

Eventual Consistency, tunable consistency

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

Key-based authentication

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.