DBMS > Hypertable vs. Linter vs. Riak KV vs. SpatiaLite

System Properties Comparison Hypertable vs. Linter vs. Riak KV vs. SpatiaLite

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.

Description

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

RDBMS for high security requirements

Distributed, fault tolerant key-value store

Spatial extension of SQLite

Primary database model

Wide column store

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

linter.ru

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

Technical documentation

www.tiot.jp/riak-docs/riak/kv/latest

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

Developer

Hypertable Inc.

relex.ru

OpenSource, formerly Basho Technologies

Alessandro Furieri

Initial release

2009

1990

2009

2008

Current release

0.9.8.11, March 2016

3.2.0, December 2022

5.0.0, August 2020

License

Commercial or Open Source

Open Source

GNU version 3. Commercial license available

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

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

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.

Implementation language

C++

C and C++

Erlang

C++

Server operating systems

Linux
OS X
Windows

an inofficial Windows port is available

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
OS X

server-less

Data scheme

schema-free

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.

Secondary indexes

restricted

only exact value or prefix value scans

yes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

C++ API
Thrift

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

HTTP API
Native Erlang Interface

Supported programming languages

C++
Java
Perl
PHP
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor on file system level

Source-replica replication

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

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

yes, using Riak Security

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

TimescaleDB goes distributed; implements ‘Chunking’ over ‘Sharding’ for scaling-out
22 August 2019, Packt Hub

SQL and TimescaleDB. This article takes a closer look into… | by Alibaba Cloud
31 July 2019, DataDrivenInvestor

Decorate your Windows XP with Hyperdesk
30 July 2008, CNET

The Collective: Customize Your Computer & Your Phone With Star Trek
18 March 2009, TrekMovie

5 Free NoSQL Database Certification Courses Online in 2024
31 January 2024, Analytics India Magazine

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

provided by Google News

Share this page