DBMS > GeoMesa vs. gStore vs. Sadas Engine vs. ToroDB

System Properties Comparison GeoMesa vs. gStore vs. Sadas Engine vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

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

A native Graph DBMS to store and maintain very large RDF datasets.

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Primary database model

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.14
Rank	#342	Overall
	#34	Graph DBMS
	#16	RDF stores

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

www.geomesa.org

en.gstore.cn

www.sadasengine.com

github.com/torodb/server

Technical documentation

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

en.gstore.cn/#/enDocs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

CCRi and others

SADAS s.r.l.

8Kdata

Initial release

2014

2016

2006

2016

Current release

5.0.0, May 2024

1.2, November 2023

8.0

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD

commercial

free trial version available

Open Source

AGPL-V3

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

Java

Server operating systems

Linux

AIX
Linux
Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free and OWL/RDFS-schema support

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

HTTP API
SPARQL 1.1

JDBC
ODBC
Proprietary protocol

Supported programming languages

C++
Java
JavaScript (Node.js)
PHP
Python

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

managed by 'Learn by Usage'

User concepts

Access control

yes

depending on the DBMS used for storage

Users, roles and permissions, Role-Based Access Control (RBAC) supported

Access rights for users, groups and roles according to SQL-standard

Access rights for users and 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.