DBMS > Databricks vs. Heroic vs. Linter vs. RocksDB

System Properties Comparison Databricks vs. Heroic vs. Linter vs. RocksDB

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

RDBMS for high security requirements

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Relational DBMS

Time Series DBMS

Relational DBMS

Key-value store

Secondary database models

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	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.databricks.com

github.com/spotify/heroic

linter.ru

rocksdb.org

Technical documentation

docs.databricks.com

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

Databricks

Spotify

relex.ru

Facebook, Inc.

Initial release

2013

2014

1990

2013

Current release

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

BSD

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

Java

C and C++

C++

Server operating systems

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

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

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

via Elasticsearch

yes

SQL

Support of SQL

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

C++ API
Java API

Supported programming languages

Python
R
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

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.