DBMS > etcd vs. GeoMesa vs. Google Cloud Firestore vs. LevelDB vs. SAP HANA

System Properties Comparison etcd vs. GeoMesa vs. Google Cloud Firestore vs. LevelDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

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

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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	7.36
Rank	#53	Overall
	#9	Document stores

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

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

www.geomesa.org

firebase.google.com/products/firestore

github.com/google/leveldb

www.sap.com/products/hana.html

Technical documentation

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

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

firebase.google.com/docs/firestore

github.com/google/leveldb/blob/main/doc/index.md

help.sap.com/hana

Developer

CCRi and others

Google

SAP

Initial release

2014

2017

2011

2010

Current release

3.4, August 2019

5.0.0, May 2024

1.23, February 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

commercial

Open Source

BSD

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

C++

Server operating systems

FreeBSD
Linux
Windows

experimental

hosted

Illumos
Linux
OS X
Windows

Appliance or cloud-service

Data scheme

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

gRPC
JSON over HTTP

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

Supported programming languages

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

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

SQLScript, R

Triggers

yes, watching key changes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

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

depending on storage layer

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

yes

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.