DBMS > AnzoGraph DB vs. Google BigQuery vs. Microsoft Azure Cosmos DB vs. Sequoiadb

System Properties Comparison AnzoGraph DB vs. Google BigQuery vs. Microsoft Azure Cosmos DB vs. Sequoiadb

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

Large scale data warehouse service with append-only tables

Globally distributed, horizontally scalable, multi-model database service

NewSQL database with distributed OLTP and SQL

Primary database model

Graph DBMS
RDF store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Relational DBMS

Secondary database models

Spatial DBMS

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	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Website

cambridgesemantics.com/anzograph

cloud.google.com/bigquery

azure.microsoft.com/services/cosmos-db

www.sequoiadb.com

Technical documentation

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

cloud.google.com/bigquery/docs

learn.microsoft.com/azure/cosmos-db

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Cambridge Semantics

Google

Microsoft

Sequoiadb Ltd.

Initial release

2018

2010

2014

2013

Current release

2.3, January 2021

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

Server: AGPL; Client: Apache V2

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

hosted

Linux

Data scheme

Schema-free and OWL/RDFS-schema support

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

oid, date, timestamp, binary, regex

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

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

yes

SQL-like query language

APIs and other access methods

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

RESTful HTTP/JSON API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

proprietary protocol using JSON

Supported programming languages

C++
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

in JavaScript

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

not needed in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Multi-item ACID transactions with snapshot isolation within a partition

Document is locked during a transaction

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights can be defined down to the item level

simple password-based access control

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.