DBMS > AnzoGraph DB vs. Google BigQuery vs. IBM Db2 Event Store vs. TinkerGraph

System Properties Comparison AnzoGraph DB vs. Google BigQuery vs. IBM Db2 Event Store vs. TinkerGraph

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

Distributed Event Store optimized for Internet of Things use cases

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Graph DBMS
RDF store

Relational DBMS

Event Store
Time Series DBMS

Graph 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	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

cambridgesemantics.com/anzograph

cloud.google.com/bigquery

www.ibm.com/products/db2-event-store

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

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

cloud.google.com/bigquery/docs

www.ibm.com/docs/en/db2-event-store

Developer

Cambridge Semantics

Google

IBM

Initial release

2018

2010

2017

2009

Current release

2.3, January 2021

2.0

License

Commercial or Open Source

commercial

free trial version available

commercial

free developer edition available

Open Source

Apache 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

C and C++

Java

Server operating systems

Linux

hosted

Linux

Linux, macOS, Windows for the developer addition

Data scheme

Schema-free and OWL/RDFS-schema support

yes

schema-free

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.

Secondary indexes

SQL

Support of SQL

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

yes

through the embedded Spark runtime

APIs and other access methods

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

RESTful HTTP/JSON API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

TinkerPop 3

Supported programming languages

C++
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

Groovy
Java

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

in JavaScript

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Active-active shard replication

none

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

Eventual Consistency

none

Foreign keys

Referential integrity

not needed in graphs

yes

Relationships in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

optional

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)

fine grained access rights according to SQL-standard

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.