DBMS > Blazegraph vs. Google BigQuery vs. HarperDB vs. IBM Cloudant

System Properties Comparison Blazegraph vs. Google BigQuery vs. HarperDB vs. IBM Cloudant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

Large scale data warehouse service with append-only tables

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Database as a Service offering based on Apache CouchDB

Primary database model

Graph DBMS
RDF store

Relational DBMS

Document store

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

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Website

blazegraph.com

cloud.google.com/bigquery

www.harperdb.io

www.ibm.com/products/cloudant

Technical documentation

wiki.blazegraph.com

cloud.google.com/bigquery/docs

docs.harperdb.io/docs

cloud.ibm.com/docs/Cloudant

Developer

Blazegraph

Google

HarperDB

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2006

2010

2017

2010

Current release

2.1.5, March 2019

3.1, August 2021

License

Commercial or Open Source

Open Source

extended commercial license available

commercial

free community edition available

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

Node.js

Erlang

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X

hosted

Data scheme

schema-free

yes

dynamic schema

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

yes

JSON data types

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

SQL

Support of SQL

SPARQL is used as query language

yes

SQL-like data manipulation statements

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Custom Functions

since release 3.1

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

A table resides as a whole on one (or more) nodes in a cluster

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

Atomic execution of specific operations

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

Durability

Support for making data persistent

yes

yes, using LMDB

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

Security and Authentication via Web Application Container (Tomcat, Jetty)

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

Access rights for users can be defined per database

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.