DBMS > Amazon Redshift vs. Databricks vs. Microsoft Azure SQL Database vs. Oracle Berkeley DB vs. Tkrzw

System Properties Comparison Amazon Redshift vs. Databricks vs. Microsoft Azure SQL Database vs. Oracle Berkeley DB vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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.

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used in-process key-value store

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

aws.amazon.com/redshift

www.databricks.com

azure.microsoft.com/en-us/products/azure-sql/database

www.oracle.com/database/technologies/related/berkeleydb.html

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/redshift

docs.databricks.com

docs.microsoft.com/en-us/azure/azure-sql

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Amazon (based on PostgreSQL)

Databricks

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Mikio Hirabayashi

Initial release

2012

2013

2010

1994

2020

Current release

V12

18.1.40, May 2020

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

Apache Version 2.0

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.

Implementation language

C++

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
macOS

Data scheme

yes

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

yes

schema-free

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

only with the Berkeley DB XML edition

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

with Databricks SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Python
R
Scala

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates

Transact SQL

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with always 3 replicas available

Source-replica replication

none

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

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

using specific database classes

User concepts

Access control

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.