DBMS > etcd vs. FatDB vs. GeoMesa vs. SAP SQL Anywhere vs. YottaDB

System Properties Comparison etcd vs. FatDB vs. GeoMesa vs. SAP SQL Anywhere vs. YottaDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A distributed reliable key-value store

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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 fast and solid embedded Key-value store

Primary database model

Key-value store

Document store
Key-value store

Spatial DBMS

Relational DBMS

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	7.03
Rank	#54	Overall
	#5	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

etcd.io
github.com/etcd-io/etcd

www.geomesa.org

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

yottadb.com

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

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

help.sap.com/docs/SAP_SQL_Anywhere

yottadb.com/resources/documentation

Developer

FatCloud

CCRi and others

SAP

formerly Sybase

YottaDB, LLC

Initial release

2012

2014

1992

2001

Current release

3.4, August 2019

5.0.0, May 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache License 2.0

commercial

Open Source

AGPL 3.0

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

Server operating systems

FreeBSD
Linux
Windows

experimental

Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Docker
Linux

Data scheme

schema-free

yes

schema-free

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

Via inetgration in SQL Server

yes

by using the Octo plugin

APIs and other access methods

gRPC
JSON over HTTP

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
HTTP API
JDBC
ODBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

via applications

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

Triggers

yes, watching key changes

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

selectable replication factor

depending on storage layer

Source-replica replication

Database mirroring

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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

yes

User concepts

Access control

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Users and groups based on OS-security mechanisms

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

Monitor Amazon EKS Control Plane metrics using AWS Open Source monitoring services | Amazon Web Services
12 October 2023, AWS Blog

Apache APISIX Without etcd?
27 July 2023, hackernoon.com

RBI reiterates need for underlying forex exposure for rupee derivatives transactions | Stock Market News
5 April 2024, Mint

Killing a market, softly: How an RBI communique could end India's thriving ETCD market
7 April 2024, The Economic Times

ETCD directives don't go well with RBI's stellar reputation
14 April 2024, Business Standard

provided by Google News

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

SAP Again Named a Leader in 2021 Gartner® Magic Quadrant™ for Cloud Database Management Systems
21 December 2021, SAP News

Rimini Street expands support beyond SAP and Oracle
9 June 2017, InsideSAP

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

Rimini Street to offer database, security services
7 June 2017, ZDNet

provided by Google News

Share this page