DBMS > AllegroGraph vs. Amazon Redshift vs. Dolt vs. MySQL

System Properties Comparison AllegroGraph vs. Amazon Redshift vs. Dolt vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance, persistent RDF store with additional support for Graph DBMS

Large scale data warehouse service for use with business intelligence tools

A MySQL compatible DBMS with Git-like versioning of data and schema

Widely used open source RDBMS

Primary database model

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

Document store

Document store
Spatial DBMS

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

Score	1.06
Rank	#187	Overall
	#30	Document stores
	#17	Graph DBMS
	#7	RDF stores
	#7	Vector DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

allegrograph.com

aws.amazon.com/redshift

github.com/dolthub/dolt
www.dolthub.com

www.mysql.com

Technical documentation

franz.com/agraph/support/documentation/current/agraph-introduction.html

docs.aws.amazon.com/redshift

docs.dolthub.com

dev.mysql.com/doc

Developer

Franz Inc.

Amazon (based on PostgreSQL)

DoltHub Inc

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2004

2012

2018

1995

Current release

8.0, December 2023

8.4.0, April 2024

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

C and C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

RDF schemas

yes

Typing

predefined data types such as float or date

yes

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.

bulk load of XML files possible

yes

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

SPARQL is used as query language

yes

does not fully support an SQL-standard

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API
SPARQL

JDBC
ODBC

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

All languages supporting JDBC/ODBC

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

JavaScript or Common Lisp

user defined functions

in Python

yes

currently in alpha release

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

with Federation

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

Only one user is configurable, and must be specified in the config file at startup

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

Knowledge Graph Platform Leader FedShard - Designed for Entity-Event Knowledge Graph...
» more

Competitive advantages

AllegroGraph is uniquely suited to support adhoc queries through SPARQL, Prolog and...
» more

News

How a Neuro-Symbolic AI Approach Can Improve Trust in AI Apps
23 May 2024

Can Neuro-Symbolic AI Solve AI’s Weaknesses?
17 April 2024

100 Companies That Matter in KM – Franz Inc.
3 April 2024

Exploring AllegroGraph v8 – Unleashing the Power of Neuro-Symbolic AI (Recorded Webinar)
9 February 2024

What is Neuro-Symbolic AI?
23 January 2024

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.