DBMS > GeoMesa vs. Heroic vs. Microsoft Azure Synapse Analytics vs. SAP Advantage Database Server vs. searchxml

System Properties Comparison GeoMesa vs. Heroic vs. Microsoft Azure Synapse Analytics vs. SAP Advantage Database Server vs. searchxml

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Low-cost RDBMS with access to ISAM and FoxPro data structures

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Spatial DBMS

Time Series DBMS

Relational DBMS

Native XML DBMS
Search engine

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	22.71
Rank	#30	Overall
	#18	Relational DBMS

Score	0.01
Rank	#386	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

www.geomesa.org

github.com/spotify/heroic

azure.microsoft.com/services/synapse-analytics

www.sap.com/products/advantage-database-server.html

www.searchxml.net/category/products

Technical documentation

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

spotify.github.io/heroic

docs.microsoft.com/azure/synapse-analytics

www.searchxml.net/support/handouts

Developer

CCRi and others

Spotify

Microsoft

Sybase, SAP

informationpartners gmbh

Initial release

2014

2016

1993

2015

Current release

4.0.5, February 2024

1.0

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

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

Scala

Java

C++

Server operating systems

hosted

Linux
Windows

Windows

Data scheme

yes

schema-free

yes

schema-free

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

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

C#
Java
PHP

Delphi
Perl
PHP

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

Transact SQL

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

yes

Transaction concepts

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

ACID

multiple readers, single writer

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

caching of (temporary) tables can be configured

User concepts

Access control

yes

depending on the DBMS used for storage

yes

fine grained access rights according to SQL-standard

Domain, group and role-based access control at the document level and for application services

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Migrate Microsoft Azure Synapse Analytics to Amazon Redshift using AWS SCT | Amazon Web Services
18 October 2023, AWS Blog

Azure Synapse Analytics: Everything you need to know about Microsoft's cloud analytics platform
24 September 2023, DataScientest

Azure Synapse vs. Databricks: Data Platform Comparison 2024
26 March 2024, eWeek

Azure Synapse Runtime for Apache Spark 3.2 End of Support | Azure updates
22 March 2024, azure.microsoft.com

Azure Synapse Link for Cosmos DB: New Analytics Capabilities
10 November 2023, InfoQ.com

provided by Google News

SAP Announces Q3 2023 Results: Asia Pacific and Japan View
19 October 2023, SAP News

AIRWORLD PART 15: WORLD'S SECOND BEST AIRPORT TERMINAL
30 September 2005, Ad Age

provided by Google News

Share this page