DBMS > HEAVY.AI vs. Lovefield vs. Riak KV vs. SpatiaLite

System Properties Comparison HEAVY.AI vs. Lovefield vs. Riak KV vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Embeddable relational database for web apps written in pure JavaScript

Distributed, fault tolerant key-value store

Spatial extension of SQLite

Primary database model

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	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	0.32
Rank	#290	Overall
	#132	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	1.72
Rank	#149	Overall
	#3	Spatial DBMS

Website

github.com/heavyai/heavydb
www.heavy.ai

google.github.io/lovefield

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

Technical documentation

docs.heavy.ai

github.com/google/lovefield/blob/master/docs/spec_index.md

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

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

Developer

HEAVY.AI, Inc.

Google

OpenSource, formerly Basho Technologies

Alessandro Furieri

Initial release

2016

2014

2009

2008

Current release

5.10, January 2022

2.1.12, February 2017

3.2.0, December 2022

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

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

JavaScript

Erlang

C++

Server operating systems

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

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

yes

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

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

Erlang

Triggers

Using read-only observers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

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

Big Data Analytics: A Game Changer for Infrastructure
13 July 2023, Spiceworks News and Insights

HEAVY.AI Launches HEAVY 7.0, Introducing Real-Time Machine Learning Capabilities
19 April 2023, Business Wire

Making the most of geospatial intelligence
14 April 2023, InfoWorld

HEAVY.AI Launches Industry's First Digital Twin for Telco Network Planning, Building and Operations
20 September 2022, Datanami

The insideBIGDATA IMPACT 50 List for Q4 2023
11 October 2023, insideBIGDATA

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

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page