DBMS > GeoMesa vs. Quasardb vs. TerminusDB

System Properties Comparison GeoMesa vs. Quasardb vs. TerminusDB

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.

Distributed, high-performance timeseries database

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

Primary database model

Spatial DBMS

Time Series DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	0.75
Rank	#204	Overall
	#3	Spatial DBMS

Score	0.07
Rank	#329	Overall
	#29	Time Series DBMS

Score	0.10
Rank	#314	Overall
	#29	Graph DBMS

Website

www.geomesa.org

quasardb.net

terminusdb.com

Technical documentation

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

doc.quasar.ai/master

terminusdb.github.io/terminusdb/#

Developer

CCRi and others

quasardb

DataChemist Ltd.

Initial release

2014

2009

2018

Current release

3.2.0, April 2021

3.13.3, April 2022

10.0.21, March 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

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

Prolog, Rust

Server operating systems

BSD
Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

SQL

Support of SQL

SQL-like query language

SQL-like query language (WOQL)

APIs and other access methods

HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

consistent hashing

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication with selectable replication factor

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

in-memory journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

Transient mode

User concepts

Access control

yes

depending on the DBMS used for storage

Cryptographically strong user authentication and audit trail

Role-based access control

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