DBMS > Amazon DynamoDB vs. BigObject vs. Machbase Neo vs. Manticore Search vs. Postgres-XL

System Properties Comparison Amazon DynamoDB vs. BigObject vs. Machbase Neo vs. Manticore Search vs. Postgres-XL

Editorial information provided by DB-Engines

Name

Description

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

Analytic DBMS for real-time computations and queries

TimeSeries DBMS for AIoT and BigData

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store
Key-value store

Relational DBMS

a hierachical model (tree) can be imposed

Time Series DBMS

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

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

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

docs.bigobject.io

machbase.com/dbms

manual.manticoresearch.com

www.postgres-xl.org/documentation

Developer

Amazon

BigObject, Inc.

Machbase

Manticore Software

Initial release

2012

2015

2013

2017

2014

since 2012, originally named StormDB

Current release

V8.0, August 2023

6.0, February 2023

10 R1, October 2018

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

free community edition available

commercial

free test version available

Open Source

GPL version 2

Open Source

Mozilla public license

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

C++

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
macOS
Windows

FreeBSD
Linux
macOS
Windows

Linux
macOS

Data scheme

schema-free

yes

Fixed schema

yes

Typing

predefined data types such as float or date

yes

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

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.

Can index from XML

yes

XML type, but no XML query functionality

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP API

fluentd
ODBC
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

Lua

user defined functions

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

volatile and lookup table

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

simple password-based 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.