DBMS > GeoMesa vs. Google Cloud Spanner vs. searchxml vs. Trafodion

System Properties Comparison GeoMesa vs. Google Cloud Spanner vs. searchxml vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

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.

DBMS for structured and unstructured content wrapped with an application server

Transactional SQL-on-Hadoop DBMS

Primary database model

Spatial DBMS

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	2.89
Rank	#105	Overall
	#53	Relational DBMS

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

Website

www.geomesa.org

cloud.google.com/spanner

www.searchxml.net/category/products

trafodion.apache.org

Technical documentation

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

cloud.google.com/spanner/docs

www.searchxml.net/support/handouts

trafodion.apache.org/documentation.html

Developer

CCRi and others

Google

informationpartners gmbh

Apache Software Foundation, originally developed by HP

Initial release

2014

2017

2015

2014

Current release

4.0.5, February 2024

1.0

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

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

C++, Java

Server operating systems

hosted

Windows

Linux

Data scheme

yes

schema-free

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.

yes

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

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
Python

C++

most other programming languages supported via APIs

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

on the application server

Java Stored Procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication with 3 replicas for regional instances.

yes

sychronisation to multiple collections

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via user defined functions and HBase

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

multiple readers, single writer

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

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)

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

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

HP Throws Trafodion Hat into OLTP Hadoop Ring
14 July 2014, Datanami

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

Low-latency, distributed database architectures are critical for emerging fog applications
7 April 2022, Embedded Computing Design

provided by Google News

Share this page