DBMS > GeoMesa vs. PlanetScale vs. SAP SQL Anywhere vs. Tkrzw vs. XTDB

System Properties Comparison GeoMesa vs. PlanetScale vs. SAP SQL Anywhere vs. Tkrzw vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

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

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

www.geomesa.org

planetscale.com

www.sap.com/products/technology-platform/sql-anywhere.html

dbmx.net/tkrzw

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

Technical documentation

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

planetscale.com/docs

help.sap.com/docs/SAP_SQL_Anywhere

www.xtdb.com/docs

Developer

CCRi and others

PlanetScale

SAP

formerly Sybase

Mikio Hirabayashi

Juxt Ltd.

Initial release

2014

2020

1992

2020

2019

Current release

5.0.1, July 2024

17, July 2015

0.9.3, August 2020

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

Open Source

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

Clojure

Server operating systems

Docker
Linux
macOS

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
macOS

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

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
MySQL protocol
ODBC

ADO.NET
HTTP API
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

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

C++
Java
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

none

yes, each node contains all data

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 across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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.

depending on storage layer

yes

using specific database classes

User concepts

Access control

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept

no user groups or roles

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

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale Insights Anomalies introduces smart query monitoring
29 November 2023, SDTimes.com

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

Top Database as a Service (DBaaS) Startups
28 August 2024, Tracxn

PlanetScale review: Horizontally scalable MySQL in the cloud
1 September 2021, InfoWorld

provided by Google News

SAP Products & Services Data Portfolio
2 July 2021, Datamation

Securing SAP with AWS Network Firewall: Part 2 – Managed Rules
17 July 2023, AWS Blog

SAP vulnerabilities Let Attacker Inject OS Commands—Patch Now!
11 July 2023, CybersecurityNews

MindsDB is now the leading and fastest growing applied ML platform in the world
3 November 2022, PR Newswire

Gartner’s Magic Quadrant for Cloud Database Management Systems
9 December 2020, CRN

provided by Google News

Share this page