DBMS > Apache Impala vs. EsgynDB vs. MySQL vs. SpatiaLite vs. Tkrzw

System Properties Comparison Apache Impala vs. EsgynDB vs. MySQL vs. SpatiaLite vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Widely used open source RDBMS

Spatial extension of SQLite

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Key-value store

Secondary database models

Document store

Document store
Spatial DBMS

Relational DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

impala.apache.org

www.esgyn.cn

www.mysql.com

www.gaia-gis.it/fossil/libspatialite/index

dbmx.net/tkrzw

Technical documentation

impala.apache.org/impala-docs.html

dev.mysql.com/doc

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Esgyn

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

Mikio Hirabayashi

Initial release

2013

2015

1995

2008

2020

Current release

4.1.0, June 2022

8.4.0, April 2024

5.0.0, August 2020

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

Apache Version 2.0

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++, Java

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

server-less

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Java Stored Procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

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

using specific database classes

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

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.