DBMS > Amazon DynamoDB vs. Heroic vs. LevelDB vs. Manticore Search

System Properties Comparison Amazon DynamoDB vs. Heroic vs. LevelDB vs. Manticore Search

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

Primary database model

Document store
Key-value store

Time Series DBMS

Key-value store

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	2.33
Rank	#111	Overall
	#19	Key-value stores

Score	0.23
Rank	#301	Overall
	#21	Search engines

Website

aws.amazon.com/dynamodb

github.com/spotify/heroic

github.com/google/leveldb

manticoresearch.com

Technical documentation

docs.aws.amazon.com/dynamodb

spotify.github.io/heroic

github.com/google/leveldb/blob/main/doc/index.md

manual.manticoresearch.com

Developer

Amazon

Spotify

Google

Manticore Software

Initial release

2012

2014

2011

2017

Current release

1.23, February 2021

6.0, February 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPL version 2

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

hosted

Illumos
Linux
OS X
Windows

FreeBSD
Linux
macOS
Windows

Data scheme

schema-free

Fixed schema

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

via Elasticsearch

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

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

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

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

by integration with AWS Lambda

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

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

with automatic compression on writes

yes

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

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 can be defined via the AWS Identity and Access Management (IAM)

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.