DBMS > Apache Impala vs. MaxDB vs. MySQL vs. SiriDB vs. Transwarp ArgoDB

System Properties Comparison Apache Impala vs. MaxDB vs. MySQL vs. SiriDB vs. Transwarp ArgoDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A robust and reliable RDBMS optimized to run all major SAP solutions

Widely used open source RDBMS

Open Source Time Series DBMS

Distributed Analytical Database to replace Hadoop+MPP hybrid architecture

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Relational DBMS

Secondary database models

Document store

Document store
Spatial DBMS

Search engine

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	0.12
Rank	#348	Overall
	#151	Relational DBMS

Website

www.transwarp.cn/en/product/argodb

Technical documentation

impala.apache.org/impala-docs.html

maxdb.sap.com/documentation

dev.mysql.com/doc

docs.siridb.com

docs.transwarp.cn/#/documents-support/docs?category=ARGODB

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

SAP, acquired from Software AG (Adabas-D) in 1997

Oracle

since 2010, originally MySQL AB, then Sun

Cesbit

Transwarp

Initial release

2013

1984

1995

2017

Current release

4.1.0, June 2022

7.9.10.12, February 2024

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Limited community edition free

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MIT License

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.

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

Implementation language

C++

C and C++

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C#
Java
Perl
PHP
Python

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

simple rights management via user accounts

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.