DBMS > Amazon CloudSearch vs. Blazegraph vs. Drizzle vs. Google BigQuery vs. Hyprcubd

System Properties Comparison Amazon CloudSearch vs. Blazegraph vs. Drizzle vs. Google BigQuery vs. Hyprcubd

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.

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Large scale data warehouse service with append-only tables

Serverless Time Series DBMS

Primary database model

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	0.81
Rank	#213	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Website

aws.amazon.com/cloudsearch

blazegraph.com

cloud.google.com/bigquery

hyprcubd.com (offline)

Technical documentation

docs.aws.amazon.com/cloudsearch

wiki.blazegraph.com

cloud.google.com/bigquery/docs

Developer

Amazon

Blazegraph

Drizzle project, originally started by Brian Aker

Google

Hyprcubd, Inc.

Initial release

2012

2006

2008

2010

Current release

2.1.5, March 2019

7.2.4, September 2012

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

GNU GPL

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

C++

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X

hosted

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

RDF literal types

yes

time, int, uint, float, string

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 search fields are automatically indexed

yes

SQL

Support of SQL

SPARQL is used as query language

yes

with proprietary extensions

yes

SQL-like query language

APIs and other access methods

HTTP API

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

JDBC

RESTful HTTP/JSON API

gRPC (https)

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

C
C++
Java
PHP

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

Multi-source replication
Source-replica replication

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

Eventual Consistency

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

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.

User concepts

Access control

authentication via encrypted signatures

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

Google Cloud Identity & Access Management (IAM)

token access

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.