DBMS > Infobright vs. Oracle Coherence vs. Oracle NoSQL vs. RocksDB

System Properties Comparison Infobright vs. Oracle Coherence vs. Oracle NoSQL vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Oracles in-memory data grid solution

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

Primary database model

Relational DBMS

Key-value store

Document store
Key-value store
Relational DBMS

Key-value store

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

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

Website

ignitetech.com/softwarelibrary/infobrightdb

www.oracle.com/java/coherence

www.oracle.com/database/nosql/technologies/nosql

rocksdb.org

Technical documentation

docs.oracle.com/en/middleware/standalone/coherence

docs.oracle.com/en/database/other-databases/nosql-database/index.html

github.com/facebook/rocksdb/wiki

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle

Facebook, Inc.

Initial release

2005

2007

2011

2013

Current release

14.1, August 2023

23.3, December 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

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

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

BSD

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

Java

C++

Server operating systems

Linux
Windows

All OS with a Java VM

Linux
Solaris SPARC/x86

Linux

Data scheme

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
JDBC
ODBC

JCache
JPA
RESTful HTTP API

RESTful HTTP API

C++ API
Java API

Supported programming languages

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

.Net
C++
Java

C
C#
Go
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Triggers

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, with selectable consistency level

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

yes

In-memory capabilities

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

yes

off heap cache

yes

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

authentification to access the cache via certificates or http basic authentication

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.