DBMS > Databricks vs. JaguarDB vs. Riak KV vs. RocksDB vs. SwayDB

System Properties Comparison Databricks vs. JaguarDB vs. Riak KV vs. RocksDB vs. SwayDB

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.

Performant, highly scalable DBMS for AI and IoT applications

Distributed, fault tolerant key-value store

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Relational DBMS

Key-value store
Vector DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

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	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

Technical documentation

docs.databricks.com

www.jaguardb.com/support.html

www.tiot.jp/riak-docs/riak/kv/latest

github.com/facebook/rocksdb/wiki

Developer

Databricks

DataJaguar, Inc.

OpenSource, formerly Basho Technologies

Facebook, Inc.

Simer Plaha

Initial release

2013

2015

2009

2013

2018

Current release

3.3 July 2023

3.2.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

Open Source

GNU Affero GPL V3.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++

the server part. Clients available in other languages

Erlang

C++

Scala

Server operating systems

hosted

Linux

Linux
OS X

Linux

Data scheme

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

Secondary indexes

yes

restricted

SQL

Support of SQL

with Databricks SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

Python
R
Scala

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions and aggregates

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

selectable replication factor

yes

none

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

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

ACID

yes

Atomic execution of operations

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

rights management via user accounts

yes, using Riak Security

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.