DBMS > Hypertable vs. LevelDB vs. MySQL vs. Teradata Aster

System Properties Comparison Hypertable vs. LevelDB vs. MySQL vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used open source RDBMS

Platform for big data analytics on multistructured data sources and types

Primary database model

Wide column store

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

github.com/google/leveldb

www.mysql.com

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

dev.mysql.com/doc

Developer

Hypertable Inc.

Google

Oracle

since 2010, originally MySQL AB, then Sun

Teradata

Initial release

2009

2011

1995

2005

Current release

0.9.8.11, March 2016

1.23, February 2021

8.4.0, April 2024

License

Commercial or Open Source

Open Source

GNU version 3. Commercial license available

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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
OS X
Windows

an inofficial Windows port is available

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

C++ API
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C++
Java
Perl
PHP
Python
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

proprietary syntax

R packages

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 on file system level

none

Multi-source replication
Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

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

with automatic compression on writes

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

Users with fine-grained authorization concept

no user groups or 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.