DBMS > Amazon Redshift vs. Datomic vs. Hypertable vs. Percona Server for MySQL vs. SpatiaLite

System Properties Comparison Amazon Redshift vs. Datomic vs. Hypertable vs. Percona Server for MySQL vs. SpatiaLite

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

An open source BigTable implementation based on distributed file systems such as Hadoop

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Spatial extension of SQLite

Primary database model

Secondary database models

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

aws.amazon.com/redshift

www.datomic.com

www.percona.com/software/mysql-database/percona-server

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

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

www.percona.com/downloads/Percona-Server-LATEST

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

Developer

Amazon (based on PostgreSQL)

Cognitect

Hypertable Inc.

Percona

Alessandro Furieri

Initial release

2012

2009

2008

Current release

1.0.6735, June 2023

0.9.8.11, March 2016

8.0.36-28, 2024

5.0.0, August 2020

License

Commercial or Open Source

commercial

limited edition free

Open Source

GNU version 3. Commercial license available

Open Source

GPL version 2

Open Source

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

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, Clojure

C++

C and C++

C++

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Windows

an inofficial Windows port is available

Linux

server-less

Data scheme

yes

schema-free

yes

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

restricted

yes

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

C++ API
Thrift

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

C++
Java
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

yes

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

selectable replication factor on file system level

Multi-source replication
Source-replica replication
XtraDB Cluster

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

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.