DBMS > Infobright vs. Ingres vs. Oracle vs. Spark SQL vs. Tarantool

System Properties Comparison Infobright vs. Ingres vs. Oracle vs. Spark SQL vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

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

Well established RDBMS

Widely used RDBMS

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

www.actian.com/databases/ingres

www.oracle.com/database

spark.apache.org/sql

www.tarantool.io

Technical documentation

docs.actian.com/ingres

docs.oracle.com/en/database

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

www.tarantool.io/en/doc

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Actian Corporation

Oracle

Apache Software Foundation

Initial release

2005

1974

originally developed at University Berkely in early 1970s

1980

2014

2008

Current release

11.2, May 2022

23c, September 2023

3.5.0 ( 2.13), September 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

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

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

Scala

C and C++

Server operating systems

Linux
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
OS X
Windows

BSD
Linux
macOS

Data scheme

yes

Schemaless in JSON and XML columns

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like DML and DDL statements

Full-featured ANSI SQL support

APIs and other access methods

ADO.NET
JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

JDBC
ODBC

Open binary protocol

Supported programming languages

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Java
Python
R
Scala

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

PL/SQL

also stored procedures in Java possible

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding, horizontal partitioning

yes, utilizing Spark Core

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Ingres Replicator

Multi-source replication
Source-replica replication

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.