DBMS > Infobright vs. RavenDB vs. SAP HANA vs. Spark SQL

System Properties Comparison Infobright vs. RavenDB vs. SAP HANA vs. Spark SQL

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

In-memory, column based data store. Available as appliance or cloud service

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

ravendb.net

www.sap.com/products/hana.html

spark.apache.org/sql

Technical documentation

ravendb.net/docs

help.sap.com/hana

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Hibernating Rhinos

SAP

Apache Software Foundation

Initial release

2005

2010

2014

Current release

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

3.5.0 ( 2.13), September 2023

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

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

Server operating systems

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Appliance or cloud-service

Linux
OS X
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

SQL

Support of SQL

yes

SQL-like query language (RQL)

yes

SQL-like DML and DDL statements

APIs and other access methods

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

JDBC
ODBC

Supported programming languages

.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

Java
Python
R
Scala

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

ACID

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Authorization levels configured per client per database

yes

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.