DBMS > Apache Impala vs. CockroachDB vs. Netezza vs. Oracle vs. Yaacomo

System Properties Comparison Apache Impala vs. CockroachDB vs. Netezza vs. Oracle vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Analytic DBMS for Hadoop

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

Data warehouse and analytics appliance part of IBM PureSystems

Widely used RDBMS

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Secondary database models

Document store

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	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

impala.apache.org

www.cockroachlabs.com

www.ibm.com/products/netezza

www.oracle.com/database

yaacomo.com

Technical documentation

impala.apache.org/impala-docs.html

www.cockroachlabs.com/docs

docs.oracle.com/en/database

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Cockroach Labs

IBM

Oracle

Q2WEB GmbH

Initial release

2013

2015

2000

1980

2009

Current release

4.1.0, June 2022

23.1.1, May 2023

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0, commercial license available

commercial

restricted free version is available

commercial

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

C and C++

Server operating systems

Linux

Linux
macOS
Windows

Linux

included in appliance

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

Android
Linux
Windows

Data scheme

yes

dynamic schema

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

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes, wire compatible with PostgreSQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

JDBC

JDBC
ODBC
OLE DB

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

C
C++
Fortran
Java
Lua
Perl
Python
R

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

Sharding, horizontal partitioning

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using RAFT

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

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

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'

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Role-based access control

Users with fine-grained authorization concept

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.