DBMS > Blazegraph vs. Google Cloud Bigtable vs. H2GIS vs. Microsoft Azure Cosmos DB vs. Tkrzw

System Properties Comparison Blazegraph vs. Google Cloud Bigtable vs. H2GIS vs. Microsoft Azure Cosmos DB vs. Tkrzw

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Spatial extension of H2

Globally distributed, horizontally scalable, multi-model database service

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Graph DBMS
RDF store

Key-value store
Wide column store

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Secondary database models

Relational DBMS

Spatial DBMS

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	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

blazegraph.com

cloud.google.com/bigtable

www.h2gis.org

azure.microsoft.com/services/cosmos-db

dbmx.net/tkrzw

Technical documentation

wiki.blazegraph.com

cloud.google.com/bigtable/docs

www.h2gis.org/docs/home

learn.microsoft.com/azure/cosmos-db

Developer

Blazegraph

Google

CNRS

Microsoft

Mikio Hirabayashi

Initial release

2006

2015

2013

2014

2020

Current release

2.1.5, March 2019

0.9.3, August 2020

License

Commercial or Open Source

Open Source

extended commercial license available

commercial

Open Source

LGPL 3.0

commercial

Open Source

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

Java

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
macOS

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

yes

JSON 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

All properties auto-indexed by default

SQL

Support of SQL

SPARQL is used as query language

yes

SQL-like query language

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

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

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

C#
C++
Go
Java
JavaScript (Node.js)
Python

Java

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

based on H2

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

based on H2

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

Transaction concepts

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

ACID

Atomic single-row operations

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

using specific database classes

User concepts

Access control

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

based on H2

Access rights can be defined down to the item level

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.