DBMS > Alibaba Cloud MaxCompute vs. Blazegraph vs. Google Cloud Datastore vs. RDF4J vs. Redis

System Properties Comparison Alibaba Cloud MaxCompute vs. Blazegraph vs. Google Cloud Datastore vs. RDF4J vs. Redis

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

MaxCompute (previously known as ODPS) is a general purpose, fully managed, multi-tenancy data processing platform for large-scale data warehousing

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

Primary database model

Relational DBMS

a graph-processing framework is available with the graphs being stored in tables

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	0.77
Rank	#214	Overall
	#98	Relational DBMS

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Website

www.alibabacloud.com/product/maxcompute

blazegraph.com

cloud.google.com/datastore

rdf4j.org

redis.com
redis.io

Technical documentation

www.alibabacloud.com/help/en/maxcompute

wiki.blazegraph.com

cloud.google.com/datastore/docs

rdf4j.org/documentation

docs.redis.com/latest/index.html
redis.io/docs

Developer

Alibaba

Blazegraph

Google

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2016

2006

2008

2004

2009

Current release

2.1.5, March 2019

7.2.4, January 2024

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

source-available extensions (modules), commercial licenses for Redis 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.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Java

Server operating systems

hosted

Linux
OS X
Windows

hosted

Linux
OS X
Unix
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

yes, details here

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

with RediSearch module

SQL

Support of SQL

SQL-like query language

SPARQL is used as query language

SQL-like query language (GQL)

with RediSQL module

APIs and other access methods

Fluentd
Flume
MaxCompute Console

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Java

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
PHP
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in Java

yes

using Google App Engine

yes

Lua; Redis Functions coming in Redis 7 (slides and Github)

Triggers

Callbacks using the Google Apps Engine

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

none

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication using Paxos

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Isolation support depends on the API used

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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)

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

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

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.