DBMS > Amazon Redshift vs. Blazegraph vs. Percona Server for MySQL vs. Rockset

System Properties Comparison Amazon Redshift vs. Blazegraph vs. Percona Server for MySQL vs. Rockset

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

Large scale data warehouse service for use with business intelligence tools

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

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Secondary database models

Relational DBMS
Search engine

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

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

Score	2.10
Rank	#119	Overall
	#57	Relational DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Website

aws.amazon.com/redshift

blazegraph.com

www.percona.com/software/mysql-database/percona-server

rockset.com

Technical documentation

docs.aws.amazon.com/redshift

wiki.blazegraph.com

www.percona.com/downloads/Percona-Server-LATEST

docs.rockset.com

Developer

Amazon (based on PostgreSQL)

Blazegraph

Percona

Rockset

Initial release

2012

2006

2008

2019

Current release

2.1.5, March 2019

8.0.36-28, 2024

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

GPL version 2

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

C++

Server operating systems

hosted

Linux
OS X
Windows

Linux

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

restricted

yes

all fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

SPARQL is used as query language

yes

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

ADO.NET
JDBC
ODBC

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication
XtraDB Cluster

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in Graphs

yes

Transaction concepts

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

ACID

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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 organizations can be defined via Rockset console

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.