DBMS > Microsoft Azure Data Explorer vs. Oracle vs. Sphinx vs. Tarantool vs. VoltDB

System Properties Comparison Microsoft Azure Data Explorer vs. Oracle vs. Sphinx vs. Tarantool vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Fully managed big data interactive analytics platform

Widely used RDBMS

Open source search engine for searching in data from different sources, e.g. relational databases

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

column oriented

Relational DBMS

Search engine

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

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

with Tarantool/GIS extension

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

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

azure.microsoft.com/services/data-explorer

www.oracle.com/database

sphinxsearch.com

www.tarantool.io

www.voltdb.com

Technical documentation

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

docs.oracle.com/en/database

sphinxsearch.com/docs

www.tarantool.io/en/doc

docs.voltdb.com

Developer

Microsoft

Oracle

Sphinx Technologies Inc.

VoltDB Inc.

Initial release

2019

1980

2001

2008

2010

Current release

cloud service with continuous releases

23c, September 2023

3.5.1, February 2023

2.10.0, May 2022

11.3, April 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence available

Open Source

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

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C and C++

C++

C and C++

Java, C++

Server operating systems

hosted

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

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

BSD
Linux
macOS

Linux
OS X

for development

Data scheme

Fixed schema with schema-less datatypes (dynamic)

yes

Schemaless in JSON and XML columns

yes

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

yes

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

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

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

all fields are automatically indexed

yes

full-text index on all search fields

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

SQL-like query language (SphinxQL)

Full-featured ANSI SQL support

yes

only a subset of SQL 99

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Proprietary protocol

Open binary protocol

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

PL/SQL

also stored procedures in Java possible

Lua, C and SQL stored procedures

Java

Triggers

yes

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

yes

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

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)

Multi-source replication
Source-replica replication

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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

FOREIGN KEY constraints are not supported

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes, write ahead logging

yes

Snapshots and command 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

Azure Active Directory Authentication

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

Users and roles with access to stored procedures

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.