DBMS > HEAVY.AI vs. Manticore Search vs. Riak TS

System Properties Comparison HEAVY.AI vs. Manticore Search vs. Riak TS

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

Multi-storage database for search, including full-text search.

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

Primary database model

Relational DBMS

Search engine

Time Series DBMS

Secondary database models

Spatial DBMS

Time Series DBMS

using the Manticore Columnar Library

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

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	0.23
Rank	#317	Overall
	#21	Search engines

Score	0.25
Rank	#308	Overall
	#26	Time Series DBMS

Website

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

manticoresearch.com

Technical documentation

docs.heavy.ai

manual.manticoresearch.com

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

Developer

HEAVY.AI, Inc.

Manticore Software

Open Source, formerly Basho Technologies

Initial release

2016

2017

2015

Current release

5.10, January 2022

6.0, February 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL version 2

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

C++ and CUDA

C++

Erlang

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

Linux
OS X

Data scheme

yes

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

restricted

SQL

Support of SQL

yes

SQL-like query language

yes, limited

APIs and other access methods

JDBC
ODBC
Thrift
Vega

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Synchronous replication based on Galera library

selectable replication factor

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

links between datasets can be stored

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

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

Recent citations in the news

HEAVY.AI Introduces HeavyIQ, Delivering Powerful Conversational Analytics Focused on Location and Time Data
19 March 2024, Datanami

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

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

provided by Google News

Vector Search in Databases: FOSDEM's Presentation on Manticore Vector Search
21 February 2024, hackernoon.com

Comparing Meilisearch and Manticore Search Using Key Benchmarks
2 May 2023, hackernoon.com

Clickhouse vs Elasticsearch vs Manticore Search Query Times With a 1.7B NYC Taxi Rides Benchmark
1 June 2022, hackernoon.com

8 Google Alternatives: How to Search Crypto, the Dark Web, More
1 February 2023, Gizmodo

TF-IDF in a nutshell. Understanding TF-IDF evolution in 5… | by Sergey Nikolaev
13 April 2020, Towards Data Science

provided by Google News

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

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

provided by Google News

Share this page