DBMS > Databend vs. Infobright vs. Oracle vs. Spark SQL

System Properties Comparison Databend vs. Infobright vs. Oracle vs. Spark SQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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

Widely used RDBMS

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

Primary database model

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

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

Score	0.30
Rank	#287	Overall
	#130	Relational DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

github.com/datafuselabs/databend
www.databend.com

ignitetech.com/softwarelibrary/infobrightdb

www.oracle.com/database

spark.apache.org/sql

Technical documentation

docs.databend.com

docs.oracle.com/en/database

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

Developer

Databend Labs

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle

Apache Software Foundation

Initial release

2021

2005

1980

2014

Current release

1.0.59, April 2023

23c, September 2023

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

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

Rust

C and C++

Scala

Server operating systems

hosted
Linux
macOS

Linux
Windows

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

Linux
OS X
Windows

Data scheme

yes

Schemaless in JSON and XML columns

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.

yes

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like DML and DDL statements

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

.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

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

isolation level can be parameterized

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

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

User concepts

Access control

Users with fine-grained authorization concept, user roles

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

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.