DBMS > Blazegraph vs. Google BigQuery vs. Oracle Rdb vs. Tarantool

System Properties Comparison Blazegraph vs. Google BigQuery vs. Oracle Rdb vs. Tarantool

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Graph DBMS
RDF store

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.74
Rank	#217	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	1.04
Rank	#184	Overall
	#84	Relational DBMS

Score	1.63
Rank	#139	Overall
	#25	Document stores
	#24	Key-value stores
	#65	Relational DBMS

Website

blazegraph.com

cloud.google.com/bigquery

www.oracle.com/database/technologies/related/rdb.html

www.tarantool.io

Technical documentation

wiki.blazegraph.com

cloud.google.com/bigquery/docs

www.oracle.com/database/technologies/related/rdb-doc.html

www.tarantool.io/en/doc

Developer

Blazegraph

Google

Oracle, originally developed by Digital Equipment Corporation (DEC)

Initial release

2006

2010

1984

2008

Current release

2.1.5, March 2019

7.4.1.1, 2021

2.10.0, May 2022

License

Commercial or Open Source

Open Source

extended commercial license available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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 and C++

Server operating systems

Linux
OS X
Windows

hosted

HP Open VMS

BSD
Linux
macOS

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

RDF literal types

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

RESTful HTTP/JSON API

Open binary protocol

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Lua, C and SQL stored procedures

Triggers

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

yes, on a single node

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, full featured in-memory storage engine with persistence

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 Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.