DBMS > CouchDB vs. Manticore Search vs. SAP HANA vs. Teradata Aster

System Properties Comparison CouchDB vs. Manticore Search vs. SAP HANA vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

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

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store

Search engine

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

couchdb.apache.org

manticoresearch.com

www.sap.com/products/hana.html

Technical documentation

docs.couchdb.org/en/stable

manual.manticoresearch.com

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Manticore Software

SAP

Teradata

Initial release

2005

2017

2010

2005

Current release

3.3.3, December 2023

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

GPL 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

Erlang

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Windows

Appliance or cloud-service

Linux

Data scheme

schema-free

Fixed schema

yes

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

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

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

in Aster File Store

Secondary indexes

yes

via views

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

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

JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

SQLScript, R

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

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

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Synchronous replication based on Galera library

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

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.