DBMS > Amazon Aurora vs. Manticore Search vs. SAP HANA vs. XTDB

System Properties Comparison Amazon Aurora vs. Manticore Search vs. SAP HANA vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

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

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Document store

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	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

aws.amazon.com/rds/aurora

manticoresearch.com

www.sap.com/products/hana.html

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

manual.manticoresearch.com

help.sap.com/hana

www.xtdb.com/docs

Developer

Amazon

Manticore Software

SAP

Juxt Ltd.

Initial release

2015

2017

2010

2019

Current release

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

Open Source

MIT License

Cloud-based only

Only available as a cloud service

yes

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++

Clojure

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

Appliance or cloud-service

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

yes

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

yes

yes, extensible-data-notation format

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.

yes

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
ODBC

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

JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

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

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication based on Galera library

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

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.