DBMS > IBM Db2 Event Store vs. IRONdb vs. Oracle vs. SAP SQL Anywhere

System Properties Comparison IBM Db2 Event Store vs. IRONdb vs. Oracle vs. SAP SQL Anywhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed Event Store optimized for Internet of Things use cases

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Widely used RDBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Event Store
Time Series DBMS

Time Series DBMS

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.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.ibm.com/products/db2-event-store

www.circonus.com/solutions/time-series-database/

www.oracle.com/database

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

www.ibm.com/docs/en/db2-event-store

docs.circonus.com/irondb/category/getting-started

docs.oracle.com/en/database

help.sap.com/docs/SAP_SQL_Anywhere

Developer

IBM

Circonus LLC.

Oracle

SAP

formerly Sybase

Initial release

2017

1980

1992

Current release

2.0

V0.10.20, January 2018

23c, September 2023

17, July 2015

License

Commercial or Open Source

commercial

free developer edition 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 and C++

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

Linux

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

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

through the embedded Spark runtime

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

yes, in Lua

PL/SQL

also stored procedures in Java possible

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

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

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

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

No - written data is immutable

yes

Durability

Support for making data persistent

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

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.