DBMS > EXASOL vs. Infobright vs. RavenDB vs. RocksDB vs. SWC-DB

System Properties Comparison EXASOL vs. Infobright vs. RavenDB vs. RocksDB vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

A high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

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

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

www.exasol.com

ignitetech.com/softwarelibrary/infobrightdb

ravendb.net

rocksdb.org

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.exasol.com/resources

ravendb.net/docs

github.com/facebook/rocksdb/wiki

Developer

Exasol

Ignite Technologies Inc.; formerly InfoBright Inc.

Hibernating Rhinos

Facebook, Inc.

Alex Kashirin

Initial release

2000

2005

2010

2013

2020

Current release

5.4, July 2022

9.2.1, May 2024

0.5, April 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

AGPL version 3, commercial license available

Open Source

BSD

Open Source

GPL V3

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

Server operating systems

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

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.

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

SQL-like query language (RQL)

SQL-like query language

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

ADO.NET
JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

Proprietary protocol
Thrift

Supported programming languages

Java
Lua
Python
R

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C++

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

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

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Authorization levels configured per client per database

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.