DBMS > GBase vs. GeoMesa vs. Ignite vs. Titan

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS

Spatial DBMS

Key-value store
Relational DBMS

Graph DBMS

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

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Website

www.gbase.cn

www.geomesa.org

ignite.apache.org

github.com/thinkaurelius/titan

Technical documentation

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

apacheignite.readme.io/docs

github.com/thinkaurelius/titan/wiki

Developer

General Data Technology Co., Ltd.

CCRi and others

Apache Software Foundation

Aurelius, owned by DataStax

Initial release

2004

2014

2015

2012

Current release

GBase 8a, GBase 8s, GBase 8c

4.0.5, February 2024

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

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, Python

Scala

C++, Java, .Net

Java

Server operating systems

Linux

Linux
OS X
Solaris
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

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

depending on storage layer

Sharding

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

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

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Security Hooks for custom implementations

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

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

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

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

DataStax acquires Aurelius, the startup behind the Titan graph database
3 February 2015, VentureBeat

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

provided by Google News

Share this page