DBMS > Databricks vs. OrigoDB vs. RocksDB vs. SAP SQL Anywhere vs. Splunk

System Properties Comparison Databricks vs. OrigoDB vs. RocksDB vs. SAP SQL Anywhere vs. Splunk

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.

A fully ACID in-memory object graph database

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Analytics Platform for Big Data

Primary database model

Document store
Relational DBMS

Document store
Object oriented DBMS

Key-value store

Relational DBMS

Search engine

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
	#53	Document stores
	#20	Object oriented DBMS

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

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.databricks.com

origodb.com

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

www.splunk.com

Technical documentation

docs.databricks.com

origodb.com/docs

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

Developer

Databricks

Robert Friberg et al

Facebook, Inc.

SAP

formerly Sybase

Splunk Inc.

Initial release

2013

2009

under the name LiveDB

2013

1992

2003

Current release

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Limited free edition and free developer edition available

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++

Server operating systems

hosted

Linux
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

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

yes

schema-free

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

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

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

with Databricks SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

Supported programming languages

Python
R
Scala

.Net

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

Source-replica replication

Database mirroring

Multi-source replication

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

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

yes

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

fine grained access rights according to SQL-standard

Access rights for users and roles

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.