DBMS > GeoMesa vs. HEAVY.AI vs. Infobright vs. Riak TS

System Properties Comparison GeoMesa vs. HEAVY.AI vs. Infobright vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Spatial DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

www.geomesa.org

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

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

docs.heavy.ai

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

Developer

CCRi and others

HEAVY.AI, Inc.

Ignite Technologies Inc.; formerly InfoBright Inc.

Open Source, formerly Basho Technologies

Initial release

2014

2016

2005

2015

Current release

5.0.0, May 2024

5.10, January 2022

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2; enterprise edition available

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

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

Scala

C++ and CUDA

Erlang

Server operating systems

Linux

Linux
Windows

Linux
OS X

Data scheme

yes

schema-free

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

Knowledge Grid Technology used instead

restricted

SQL

Support of SQL

yes

yes, limited

APIs and other access methods

JDBC
ODBC
Thrift
Vega

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
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

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Round robin

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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, businesswire.com

Making the most of geospatial intelligence
14 April 2023, InfoWorld

OmniSci Gets HEAVY New Name and New CEO
1 March 2022, Datanami

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

provided by Google News

Ignite Buys Database Vendor Infobright
2 May 2017, Datanami

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page