DBMS > EsgynDB vs. GeoMesa vs. SAP SQL Anywhere vs. ToroDB vs. Vitess

System Properties Comparison EsgynDB vs. GeoMesa vs. SAP SQL Anywhere vs. ToroDB vs. Vitess

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

www.esgyn.cn

www.geomesa.org

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

github.com/torodb/server

vitess.io

Technical documentation

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

help.sap.com/docs/SAP_SQL_Anywhere

vitess.io/docs

Developer

Esgyn

CCRi and others

SAP

formerly Sybase

8Kdata

The Linux Foundation, PlanetScale

Initial release

2015

2014

1992

2016

2013

Current release

5.0.0, May 2024

17, July 2015

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

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

C++, Java

Scala

Java

Server operating systems

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

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

Java Stored Procedures

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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

depending on storage layer

Source-replica replication

Database mirroring

Source-replica replication

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

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency
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 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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Access rights for users and roles

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 vulnerabilities Let Attacker Inject OS Commands—Patch Now!
11 July 2023, CybersecurityNews

SAP Products & Services Data Portfolio
2 July 2021, Datamation

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

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

SAP launches HANA cloud platform, partners with Siemens, Intel
6 May 2015, Channel Daily News

provided by Google News

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

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

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

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

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page