DBMS > Databricks vs. IBM Cloudant vs. SAP HANA vs. ToroDB vs. Warp 10

System Properties Comparison Databricks vs. IBM Cloudant vs. SAP HANA vs. ToroDB vs. Warp 10

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded 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.

Database as a Service offering based on Apache CouchDB

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

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.databricks.com

www.ibm.com/products/cloudant

www.sap.com/products/hana.html

github.com/torodb/server

www.warp10.io

Technical documentation

docs.databricks.com

cloud.ibm.com/docs/Cloudant

help.sap.com/hana

www.warp10.io/content/02_Getting_started

Developer

Databricks

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

SAP

8Kdata

SenX

Initial release

2013

2010

2016

2015

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

AGPL-V3

Open Source

Apache License 2.0

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

Erlang

Java

Server operating systems

hosted

Appliance or cloud-service

All OS with a Java 7 VM

Linux
OS X
Windows

Data scheme

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

schema-free

yes

schema-free

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

SQL

Support of SQL

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

Python
R
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

View functions (Map-Reduce) in JavaScript

SQLScript, R

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

yes

Access rights for users and roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.