DBMS > GeoMesa vs. PostgreSQL vs. Titan

System Properties Comparison GeoMesa vs. PostgreSQL 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

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

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Spatial DBMS

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Graph DBMS

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

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

Score	0.75
Rank	#212	Overall
	#4	Spatial DBMS

Score	663.42
Rank	#4	Overall
	#4	Relational DBMS

Website

www.geomesa.org

www.postgresql.org

github.com/thinkaurelius/titan

Technical documentation

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

www.postgresql.org/docs

github.com/thinkaurelius/titan/wiki

Developer

CCRi and others

PostgreSQL Global Development Group

www.postgresql.org/developer

Aurelius, owned by DataStax

Initial release

2014

1989

1989: Postgres, 1996: PostgreSQL

2012

Current release

5.0.1, July 2024

16.4, August 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD

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.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

Scala

Java

Server operating systems

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

yes

standard with numerous extensions

APIs and other access methods

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

partitioning by range, list and (since PostgreSQL 11) by hash

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

other methods possible by using 3rd party extensions

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

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

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

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.