DBMS > Cachelot.io vs. Manticore Search vs. Riak TS vs. ToroDB

System Properties Comparison Cachelot.io vs. Manticore Search vs. Riak TS vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

In-memory caching system

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Website

cachelot.io

manticoresearch.com

github.com/torodb/server

Technical documentation

manual.manticoresearch.com

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

Developer

Manticore Software

Open Source, formerly Basho Technologies

8Kdata

Initial release

2015

2017

2015

2016

Current release

6.0, February 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

GPL version 2

Open Source

AGPL-V3

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

Java

Server operating systems

FreeBSD
Linux
OS X

FreeBSD
Linux
macOS
Windows

Linux
OS X

All OS with a Java 7 VM

Data scheme

schema-free

Fixed schema

schema-free

Typing

predefined data types such as float or date

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

yes

string, integer, double, boolean, date, object_id

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

SQL-like query language

yes, limited

APIs and other access methods

Memcached protocol

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

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

none

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Eventual Consistency
Immediate 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.

User concepts

Access control

Access rights for users and roles

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

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

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Integrating Manticore Search with Apache Superset
8 August 2023, hackernoon.com

Highlighting in Search Results
24 May 2020, hackernoon.com

40 Stories To Learn About Elasticsearch
27 April 2023, hackernoon.com

provided by Google News

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

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

provided by Google News

Share this page