DBMS > Heroic vs. Manticore Search vs. Microsoft Azure Table Storage vs. Oracle Rdb vs. SQLite

System Properties Comparison Heroic vs. Manticore Search vs. Microsoft Azure Table Storage vs. Oracle Rdb vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

A Wide Column Store for rapid development using massive semi-structured datasets

Widely used embeddable, in-process RDBMS

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.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/spotify/heroic

manticoresearch.com

azure.microsoft.com/en-us/services/storage/tables

www.oracle.com/database/technologies/related/rdb.html

www.sqlite.org

Technical documentation

spotify.github.io/heroic

manual.manticoresearch.com

www.oracle.com/database/technologies/related/rdb-doc.html

www.sqlite.org/docs.html

Developer

Spotify

Manticore Software

Microsoft

Oracle, originally developed by Digital Equipment Corporation (DEC)

Dwayne Richard Hipp

Initial release

2014

2017

2012

1984

2000

Current release

6.0, February 2023

7.4.1.1, 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2

commercial

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

FreeBSD
Linux
macOS
Windows

hosted

HP Open VMS

server-less

Data scheme

schema-free

Fixed schema

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

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

yes

not rigid because of 'dynamic typing' concept.

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

via Elasticsearch

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

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

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

optimistic locking

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights based on private key authentication or shared access signatures

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.