DBMS > Amazon Neptune vs. Heroic vs. Microsoft Azure Table Storage vs. MySQL vs. OpenEdge

System Properties Comparison Amazon Neptune vs. Heroic vs. Microsoft Azure Table Storage vs. MySQL vs. OpenEdge

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A Wide Column Store for rapid development using massive semi-structured datasets

Widely used open source RDBMS

Application development environment with integrated database management system

Primary database model

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Website

aws.amazon.com/neptune

github.com/spotify/heroic

azure.microsoft.com/en-us/services/storage/tables

www.mysql.com

www.progress.com/openedge

Technical documentation

aws.amazon.com/neptune/developer-resources

spotify.github.io/heroic

dev.mysql.com/doc

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Amazon

Spotify

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Progress Software Corporation

Initial release

2017

2014

2012

1995

1984

Current release

8.4.0, April 2024

OpenEdge 12.2, March 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

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

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

close to SQL 92

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

HQL (Heroic Query Language, a JSON-based language)
HTTP API

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
C#
C++
Java
JavaScript (Node.js)
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

Progress proprietary ABL (Advanced Business Language)

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

since Version 11.4

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica 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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

optimistic locking

ACID

not for MyISAM storage engine

ACID

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

with encyption-at-rest

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 can be defined via the AWS Identity and Access Management (IAM)

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept

no user groups or roles

Users and groups

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.