DBMS > GeoMesa vs. MarkLogic vs. Sadas Engine vs. SAP HANA vs. Teradata Aster

System Properties Comparison GeoMesa vs. MarkLogic vs. Sadas Engine vs. SAP HANA vs. Teradata Aster

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Operational and transactional Enterprise NoSQL database

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Spatial DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

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.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.geomesa.org

www.marklogic.com

www.sadasengine.com

www.sap.com/products/hana.html

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

docs.marklogic.com

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

help.sap.com/hana

Developer

CCRi and others

MarkLogic Corp.

SADAS s.r.l.

SAP

Teradata

Initial release

2014

2001

2006

2010

2005

Current release

4.0.5, February 2024

11.0, December 2022

8.0

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

commercial

free trial version available

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

Scala

C++

Server operating systems

Linux
OS X
Windows

AIX
Linux
Windows

Appliance or cloud-service

Linux

Data scheme

yes

schema-free

Schema can be enforced

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

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.

yes

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

SQL92

yes

APIs and other access methods

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

JDBC
ODBC
Proprietary protocol

JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

SQLScript, R

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

none

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

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

depending on storage layer

yes, with Range Indexes

yes

managed by 'Learn by Usage'

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Role-based access control at the document and subdocument levels

Access rights for users, groups and roles according to SQL-standard

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.