DBMS > Databricks vs. Hypertable vs. MySQL vs. OpenEdge

System Properties Comparison Databricks vs. Hypertable vs. MySQL vs. OpenEdge

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

An open source BigTable implementation based on distributed file systems such as Hadoop

Widely used open source RDBMS

Application development environment with integrated database management system

Primary database model

Document store
Relational DBMS

Wide column store

Relational DBMS

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	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Website

www.databricks.com

www.mysql.com

www.progress.com/openedge

Technical documentation

docs.databricks.com

dev.mysql.com/doc

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Databricks

Hypertable Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Progress Software Corporation

Initial release

2013

2009

1995

1984

Current release

0.9.8.11, March 2016

8.3.0, January 2024

OpenEdge 12.2, March 2020

License

Commercial or Open Source

commercial

Open Source

GNU version 3. Commercial license available

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

C++

C and C++

Server operating systems

hosted

Linux
OS X
Windows

an inofficial Windows port is available

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

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

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

with Databricks SQL

yes

with proprietary extensions

yes

close to SQL 92

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

C++ API
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

Python
R
Scala

C++
Java
Perl
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

user defined functions and aggregates

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

selectable replication factor on file system level

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

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

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

no user groups or roles

Users and groups

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.