DBMS > Amazon DocumentDB vs. Blazegraph vs. MySQL vs. ToroDB

System Properties Comparison Amazon DocumentDB vs. Blazegraph vs. MySQL vs. ToroDB

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.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

Widely used open source RDBMS

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store

Graph DBMS
RDF store

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/documentdb

blazegraph.com

www.mysql.com

github.com/torodb/server

Technical documentation

aws.amazon.com/documentdb/resources

wiki.blazegraph.com

dev.mysql.com/doc

Developer

Blazegraph

Oracle

since 2010, originally MySQL AB, then Sun

8Kdata

Initial release

2019

2006

1995

2016

Current release

2.1.5, March 2019

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL-V3

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Java

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

yes

string, integer, double, boolean, date, object_id

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SPARQL is used as query language

yes

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Relationships in Graphs

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-document operations

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Access rights for users and roles

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for 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.