DBMS > Lovefield vs. RocksDB vs. Splice Machine vs. Splunk vs. SQream DB

System Properties Comparison Lovefield vs. RocksDB vs. Splice Machine vs. Splunk vs. SQream DB

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Analytics Platform for Big Data

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

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

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

google.github.io/lovefield

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

github.com/facebook/rocksdb/wiki

splicemachine.com/how-it-works

docs.splunk.com/Documentation/Splunk

docs.sqream.com

Developer

Google

Facebook, Inc.

Splice Machine

Splunk Inc.

SQream Technologies

Initial release

2014

2013

2014

2003

2017

Current release

2.1.12, February 2017

9.2.1, May 2024

3.1, March 2021

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

Open Source

AGPL 3.0, commercial license available

commercial

Limited free edition and free developer edition available

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

JavaScript

C++

Java

C++, CUDA, Haskell, Java, Scala

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

SQL-like query language

via JavaScript builder pattern

yes

Splunk Search Processing Language for search commands

yes

APIs and other access methods

C++ API
Java API

JDBC
Native Spark Datasource
ODBC

HTTP REST

.Net
JDBC
ODBC

Supported programming languages

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Java

yes

user defined functions in Python

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

Access rights for users and roles

More information provided by the system vendor

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.