DBMS > Badger vs. Manticore Search vs. RethinkDB vs. SAP HANA vs. Yaacomo

System Properties Comparison Badger vs. Manticore Search vs. RethinkDB vs. SAP HANA vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

In-memory, column based data store. Available as appliance or cloud service

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	2.66
Rank	#107	Overall
	#20	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/dgraph-io/badger

manticoresearch.com

rethinkdb.com

www.sap.com/products/hana.html

yaacomo.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

manual.manticoresearch.com

rethinkdb.com/docs

help.sap.com/hana

Developer

DGraph Labs

Manticore Software

The Linux Foundation

since July 2017

SAP

Q2WEB GmbH

Initial release

2017

2009

2010

2009

Current release

6.0, February 2023

2.4.1, August 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2

Open Source

Apache Version 2

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Windows

Linux
OS X
Windows

Appliance or cloud-service

Android
Linux
Windows

Data scheme

schema-free

Fixed schema

schema-free

yes

Typing

predefined data types such as float or date

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

yes

string, binary, float, bool, date, geometry

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

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

JDBC
ODBC

Supported programming languages

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

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding

range based

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

Source-replica replication

yes

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

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

yes

users and table-level permissions

yes

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.