DBMS > Databricks vs. etcd vs. MySQL vs. Postgres-XL

System Properties Comparison Databricks vs. etcd vs. MySQL vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

A distributed reliable key-value store

Widely used open source RDBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store
Relational DBMS

Key-value 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	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

www.databricks.com

etcd.io
github.com/etcd-io/etcd

www.mysql.com

www.postgres-xl.org

Technical documentation

docs.databricks.com

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

dev.mysql.com/doc

www.postgres-xl.org/documentation

Developer

Databricks

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

1995

2014

since 2012, originally named StormDB

Current release

3.4, August 2019

8.4.0, April 2024

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Mozilla public license

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

hosted

FreeBSD
Linux
Windows

experimental

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

with Databricks SQL

yes

with proprietary extensions

yes

distributed, parallel query execution

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

gRPC
JSON over HTTP

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Python
R
Scala

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

proprietary syntax

user defined functions

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

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

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

MVCC

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

fine grained access rights according to SQL-standard

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.