DBMS > EsgynDB vs. GeoMesa vs. Postgres-XL vs. Titan

System Properties Comparison EsgynDB vs. GeoMesa vs. Postgres-XL vs. Titan

Please select another system to include it in the comparison.

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

www.esgyn.cn

www.geomesa.org

www.postgres-xl.org

github.com/thinkaurelius/titan

Technical documentation

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

www.postgres-xl.org/documentation

github.com/thinkaurelius/titan/wiki

Developer

Esgyn

CCRi and others

Aurelius, owned by DataStax

Initial release

2015

2014

since 2012, originally named StormDB

2012

Current release

5.0.0, May 2024

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Mozilla public license

Open Source

Apache license, version 2.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

C++, Java

Scala

Java

Server operating systems

Linux

Linux
macOS

Linux
OS X
Unix
Windows

Data scheme

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Clojure
Java
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

horizontal partitioning

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

depending on storage layer

yes

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

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual 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

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

In-memory capabilities

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

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

User authentification and security via Rexster Graph Server

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

Titan Graph Database Integration with DynamoDB: World-class Performance, Availability, and Scale for New Workloads
20 August 2015, All Things Distributed

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

5 Q's with Graph Database Expert Marko Rodriguez – Center for Data Innovation
9 November 2013, Center for Data Innovation

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

provided by Google News

Share this page