DBMS > Ingres vs. Microsoft Azure Data Explorer vs. MySQL vs. Splunk vs. Trafodion

System Properties Comparison Ingres vs. Microsoft Azure Data Explorer vs. MySQL vs. Splunk vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Well established RDBMS

Fully managed big data interactive analytics platform

Widely used open source RDBMS

Analytics Platform for Big Data

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Search engine

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
Spatial DBMS

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

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.actian.com/databases/ingres

azure.microsoft.com/services/data-explorer

www.mysql.com

www.splunk.com

trafodion.apache.org

Technical documentation

docs.actian.com/ingres

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

dev.mysql.com/doc

docs.splunk.com/Documentation/Splunk

trafodion.apache.org/documentation.html

Developer

Actian Corporation

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Splunk Inc.

Apache Software Foundation, originally developed by HP

Initial release

1974

originally developed at University Berkely in early 1970s

2019

1995

2003

2014

Current release

11.2, May 2022

cloud service with continuous releases

8.4.0, April 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Limited free edition and free developer edition available

Open Source

Apache 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++, Java

Server operating systems

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

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

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

Splunk Search Processing Language for search commands

yes

APIs and other access methods

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java
JavaScript
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

yes

Java Stored Procedures

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

yes

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

Multi-source replication
Source-replica replication

Multi-source replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

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

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

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.