DBMS > AnzoGraph DB vs. Google BigQuery vs. Riak TS vs. Sadas Engine

System Properties Comparison AnzoGraph DB vs. Google BigQuery vs. Riak TS vs. Sadas Engine

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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

cambridgesemantics.com/anzograph

cloud.google.com/bigquery

www.sadasengine.com

Technical documentation

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

cloud.google.com/bigquery/docs

www.tiot.jp/riak-docs/riak/ts/latest

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Cambridge Semantics

Google

Open Source, formerly Basho Technologies

SADAS s.r.l.

Initial release

2018

2010

2015

2006

Current release

2.3, January 2021

3.0.0, September 2022

8.0

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

commercial

free trial version available

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

C++

Server operating systems

Linux

hosted

Linux
OS X

AIX
Linux
Windows

Data scheme

Schema-free and OWL/RDFS-schema support

yes

schema-free

yes

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

restricted

yes

SQL

Support of SQL

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

yes

yes, limited

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

HTTP API
Native Erlang Interface

JDBC
ODBC
Proprietary protocol

Supported programming languages

C++
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

in JavaScript

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

selectable replication factor

none

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

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

links between datasets can be stored

yes

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

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

managed by 'Learn by Usage'

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 for users, groups and roles 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.