DBMS > Drizzle vs. Heroic vs. OpenEdge vs. ToroDB vs. Vitess

System Properties Comparison Drizzle vs. Heroic vs. OpenEdge vs. ToroDB vs. Vitess

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Application development environment with integrated database management system

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

github.com/spotify/heroic

www.progress.com/openedge

github.com/torodb/server

vitess.io

Technical documentation

spotify.github.io/heroic

documentation.progress.com/output/ua/OpenEdge_latest

vitess.io/docs

Developer

Drizzle project, originally started by Brian Aker

Spotify

Progress Software Corporation

8Kdata

The Linux Foundation, PlanetScale

Initial release

2008

2014

1984

2016

2013

Current release

7.2.4, September 2012

OpenEdge 12.2, March 2020

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

commercial

Open Source

AGPL-V3

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

FreeBSD
Linux
OS X

AIX
HP-UX
Linux
Solaris
Windows

All OS with a Java 7 VM

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

with proprietary extensions

APIs and other access methods

JDBC

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

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C++
Java
PHP

Progress proprietary ABL (Advanced Business Language)

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

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Source-replica replication

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users and groups

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

OpenEdge Application Development | Progress OpenEdge
14 September 2014, Progress Software

What's New in OpenEdge 12.8
15 April 2024, Release.nl

PoC Exploit Released for OpenEdge Authentication Gateway & AdminServer Vulnerability
11 March 2024, GBHackers

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

PlanetScale offers undo button to reverse schema migration without losing data
24 March 2022, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page