DBMS > Heroic vs. IBM Db2 vs. Microsoft Azure Data Explorer vs. Oracle vs. Solr

System Properties Comparison Heroic vs. IBM Db2 vs. Microsoft Azure Data Explorer vs. Oracle vs. Solr

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Common in IBM host environments, 2 different versions for host and Windows/Linux

Fully managed big data interactive analytics platform

Widely used RDBMS

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Time Series DBMS

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

column oriented

Relational DBMS

Search engine

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

github.com/spotify/heroic

www.ibm.com/products/db2

azure.microsoft.com/services/data-explorer

www.oracle.com/database

solr.apache.org

Technical documentation

spotify.github.io/heroic

www.ibm.com/docs/en/db2

docs.microsoft.com/en-us/azure/data-explorer

docs.oracle.com/en/database

solr.apache.org/resources.html

Developer

Spotify

IBM

Microsoft

Oracle

Apache Software Foundation

Initial release

2014

1983

host version

2019

1980

2006

Current release

12.1, October 2016

cloud service with continuous releases

23c, September 2023

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free version is available

commercial

restricted free version is available

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C and C++

Java

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows
z/OS

hosted

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

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

yes

Fixed schema with schema-less datatypes (dynamic)

yes

Schemaless in JSON and XML columns

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

yes

supports customizable data types and automatic typing

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

via Elasticsearch

yes

all fields are automatically indexed

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

Solr Parallel SQL Interface

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Java API
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

.Net
Go
Java
JavaScript (Node.js)
PowerShell
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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

PL/SQL

also stored procedures in Java possible

Java plugins

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

can be realized in PL/SQL

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual 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

optimistic locking

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

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

fine grained access rights according to SQL-standard

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.