DBMS > Infobright vs. ObjectBox vs. RocksDB vs. Sphinx vs. Splice Machine

System Properties Comparison Infobright vs. ObjectBox vs. RocksDB vs. Sphinx vs. Splice Machine

Editorial information provided by DB-Engines

Name

Description

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Extremely fast embedded database for small devices, IoT and Mobile

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

Open source search engine for searching in data from different sources, e.g. relational databases

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

Primary database model

Secondary database models

Time Series DBMS

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

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	1.22
Rank	#172	Overall
	#5	Object oriented DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	6.03
Rank	#60	Overall
	#6	Search engines

Score	0.54
Rank	#255	Overall
	#116	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

docs.objectbox.io

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

splicemachine.com/how-it-works

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

ObjectBox Limited

Facebook, Inc.

Sphinx Technologies Inc.

Splice Machine

Initial release

2005

2017

2013

2001

2014

Current release

8.11.4, April 2024

3.5.1, February 2023

3.1, March 2021

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache License 2.0

Open Source

BSD

Open Source

GPL version 2, commercial licence available

Open Source

AGPL 3.0, commercial license available

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

C and C++

C++

Java

Server operating systems

Linux
Windows

Android
iOS
Linux
macOS
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

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.

Secondary indexes

Knowledge Grid Technology used instead

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Proprietary native API

C++ API
Java API

Proprietary protocol

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

online/offline synchronization between client and server

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

exploiting MySQL or PostgreSQL frontend capabilities

yes

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

More information provided by the system vendor

News

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

Vector Database Release for Flutter / Dart + Python
13 June 2023

SQLite and SQLite alternatives – a comprehensive overview
7 June 2023

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.