DBMS > Databricks vs. Firebase Realtime Database vs. SAP HANA vs. VoltDB vs. WakandaDB

System Properties Comparison Databricks vs. Firebase Realtime Database vs. SAP HANA vs. VoltDB vs. WakandaDB

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.

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

In-memory, column based data store. Available as appliance or cloud service

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Object oriented DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
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	14.29
Rank	#39	Overall
	#6	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.databricks.com

firebase.google.com/products/realtime-database

www.sap.com/products/hana.html

www.voltdb.com

wakanda.github.io

Technical documentation

docs.databricks.com

firebase.google.com/docs/database

help.sap.com/hana

docs.voltdb.com

wakanda.github.io/doc

Developer

Databricks

Google

acquired by Google 2014

SAP

VoltDB Inc.

Wakanda SAS

Initial release

2013

2012

2010

2012

Current release

2.0 SPS07 (April 4, 2023), April 2023

11.3, April 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Open Source

AGPLv3, extended commercial license available

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java, C++

C++, JavaScript

Server operating systems

hosted

Appliance or cloud-service

Linux
OS X

for development

Linux
OS X
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

SQL

Support of SQL

with Databricks SQL

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

Python
R
Scala

Java
JavaScript
Objective-C

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

JavaScript

Server-side scripts

Stored procedures

user defined functions and aggregates

limited functionality with using 'rules'

SQLScript, R

Java

yes

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

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

yes, based on authentication and database rules

yes

Users and roles with access to stored procedures

yes

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.