DBMS > Apache Impala vs. FatDB vs. Riak KV vs. SpatiaLite

System Properties Comparison Apache Impala vs. FatDB vs. Riak KV vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Analytic DBMS for Hadoop

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Distributed, fault tolerant key-value store

Spatial extension of SQLite

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

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

Spatial DBMS

Secondary database models

Document store

Relational DBMS

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	1.56
Rank	#142	Overall
	#3	Spatial DBMS

Website

impala.apache.org

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

Technical documentation

impala.apache.org/impala-docs.html

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

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

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

FatCloud

OpenSource, formerly Basho Technologies

Alessandro Furieri

Initial release

2013

2012

2009

2008

Current release

4.1.0, June 2022

3.2.0, December 2022

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2

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

Erlang

C++

Server operating systems

Linux

Windows

Linux
OS X

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Via inetgration in SQL Server

yes

APIs and other access methods

JDBC
ODBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

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

user defined functions and integration of map-reduce

yes

via applications

Erlang

Triggers

yes

via applications

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

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

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Can implement custom security layer via applications

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

Apache Impala 4 Supports Operator Multi-Threading
29 July 2021, iProgrammer

Apache Impala becomes Top-Level Project
28 November 2017, SDTimes.com

Cloudera brings Apache Iceberg data lake format to its Data Platform
30 June 2022, SiliconANGLE News

Hudi: Uber Engineering’s Incremental Processing Framework on Apache Hadoop
12 March 2017, Uber

Updates & Upserts in Hadoop Ecosystem with Apache Kudu
27 October 2017, KDnuggets

provided by Google News

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

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Top 8 Best NoSQL Databases in 2024
9 September 2024, AIM

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

Basho aims for enterprise operational simplicity with new Data Platform
26 May 2015, diginomica

provided by Google News

Share this page