DBMS > GeoMesa vs. Google Cloud Spanner vs. SAP Adaptive Server vs. Transbase

System Properties Comparison GeoMesa vs. Google Cloud Spanner vs. SAP Adaptive Server vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.geomesa.org

cloud.google.com/spanner

www.sap.com/products/technology-platform/sybase-ase.html

www.transaction.de/en/products/transbase.html

Technical documentation

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

cloud.google.com/spanner/docs

help.sap.com/docs/SAP_ASE

www.transaction.de/en/products/transbase/features.html

Developer

CCRi and others

Google

SAP, Sybase

Transaction Software GmbH

Initial release

2014

2017

1987

Current release

4.0.5, February 2024

16.0

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free development license

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

C and C++

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Unix
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

yes

APIs and other access methods

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Java
JavaScript (Node.js)
Python

C
C++
Cobol
Java
Java
Perl
PHP
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Java and Transact-SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication with 3 replicas for regional instances.

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Transaction concepts

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

ACID

Strict serializable isolation

ACID

yes

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

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.

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

Google Improves Cloud Spanner: More Compute and Storage without Price Increase
14 October 2023, InfoQ.com

Google turns up the heat on AWS, claims Cloud Spanner is half the cost of DynamoDB
11 October 2023, TechCrunch

Google makes its Cloud Spanner database service faster and more cost-efficient
11 October 2023, SiliconANGLE News

Google Spanner: When Do You Need to Move to It?
11 September 2023, hackernoon.com

Google Cloud Spanner competes directly with Amazon DynamoDB
12 October 2023, Techzine Europe

provided by Google News

New Services in SAP HANA Cloud Lower TCO for Customers in Data-Intensive, Highly Regulated Industries
7 April 2021, SAP News

Arcion Introduces SAP Sybase ASE Connector for Ultimate Migration Flexibility
5 January 2023, businesswire.com

Patch SAP Adaptive Server Enterprise now to avoid takeover risk
3 June 2020, BleepingComputer

Newly Patched SAP ASE Flaws Could Let Attackers Hack Database Servers
3 June 2020, The Hacker News

New Feature: SAP ASE Database Available for the IBM Cloud for SAP NetWeaver Offering
22 March 2019, ibm.com

provided by Google News

Share this page