DBMS > GeoMesa vs. MaxDB vs. TerminusDB vs. Vitess

System Properties Comparison GeoMesa vs. MaxDB vs. TerminusDB vs. Vitess

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 robust and reliable RDBMS optimized to run all major SAP solutions

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
RDF store

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	2.15
Rank	#115	Overall
	#55	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

Technical documentation

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

maxdb.sap.com/documentation

terminusdb.github.io/terminusdb/#

vitess.io/docs

Developer

CCRi and others

SAP, acquired from Software AG (Adabas-D) in 1997

DataChemist Ltd.

The Linux Foundation, PlanetScale

Initial release

2014

1984

2018

2013

Current release

5.0.1, July 2024

7.9.10.12, February 2024

11.0.0, January 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Limited community edition free

Open Source

GPL V3

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C++

Prolog, Rust

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

Linux

Docker
Linux
macOS

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

SQL-like query language (WOQL)

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC
WebDAV

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
C#
Java
Perl
PHP
Python

JavaScript
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

Journaling Streams

Multi-source replication
Source-replica replication

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

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

in-memory journaling

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

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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

SAP Content Server High Availability using Amazon EFS and SUSE
30 December 2020, AWS Blog

What is SAP S/4HANA?
21 March 2022, TechTarget

Hana triumphs, MaxDB lives on
24 September 2015, E3-Magazin

Google Cloud adds backup vaults and centralized management
10 September 2024, Blocks & Files

Researcher finds flaw in SAP's MaxDB
10 January 2008, ZDNet

provided by Google News

How TerminusDB is commercializing its open source graph database
16 March 2021, VentureBeat

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

Bus Terminus Update – April 26th
26 April 2021, Around DB and Life on Lantau

provided by Google News

Deepthi Sigireddi on Distributed Database Architecture in the Cloud Native Era
20 May 2024, InfoQ.com

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale offers undo button to reverse schema migration without losing data
24 March 2022, The Register

CNCF’s Vitess Scales MySQL with the Help of Kubernetes
9 February 2018, The New Stack

provided by Google News

Share this page