DBMS > GeoMesa vs. NSDb vs. Sadas Engine vs. Titan vs. WakandaDB

System Properties Comparison GeoMesa vs. NSDb vs. Sadas Engine vs. Titan vs. WakandaDB

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

Titan is a Graph DBMS optimized for distributed clusters.

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.geomesa.org

nsdb.io

www.sadasengine.com

github.com/thinkaurelius/titan

wakanda.github.io

Technical documentation

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

nsdb.io/Architecture

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

github.com/thinkaurelius/titan/wiki

wakanda.github.io/doc

Developer

CCRi and others

SADAS s.r.l.

Aurelius, owned by DataStax

Wakanda SAS

Initial release

2014

2017

2006

2012

Current release

4.0.5, February 2024

8.0

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

commercial

free trial version available

Open Source

Apache license, version 2.0

Open Source

AGPLv3, extended commercial license 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

Scala

Java, Scala

C++

Java

C++, JavaScript

Server operating systems

Linux
macOS

AIX
Linux
Windows

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

gRPC
HTTP REST
WebSocket

JDBC
ODBC
Proprietary protocol

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

RESTful HTTP API

Supported programming languages

Java
Scala

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

Clojure
Java
Python

JavaScript

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

yes

via pluggable storage backends

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

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

Using Apache Lucene

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

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

User authentification and security via Rexster Graph Server

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.

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

Graph DBMS increased their popularity by 500% within the last 2 years
3 March 2015, Paul Andlinger

Graph DBMSs are gaining in popularity faster than any other database category
21 January 2014, Matthias Gelbmann

show all

Recent citations in the news

Amazon DynamoDB Storage Backend for Titan: Distributed Graph Database | Amazon Web Services
24 August 2015, AWS Blog

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

DSE Graph review: Graph database does double duty
14 November 2019, InfoWorld

Database Deep Dives: JanusGraph
8 August 2019, IBM

Beyond Titan: The Evolution of DataStax's New Graph Database
21 June 2016, Datanami

provided by Google News

Share this page