DBMS > GeoMesa vs. Graphite vs. GridDB vs. Trafodion

System Properties Comparison GeoMesa vs. Graphite vs. GridDB vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Scalable in-memory time series database optimized for IoT and Big Data

Transactional SQL-on-Hadoop DBMS

Primary database model

Spatial DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	5.19
Rank	#62	Overall
	#4	Time Series DBMS

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Website

www.geomesa.org

github.com/graphite-project/graphite-web

griddb.net

trafodion.apache.org

Technical documentation

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

graphite.readthedocs.io

docs.griddb.net

trafodion.apache.org/documentation.html

Developer

CCRi and others

Chris Davis

Toshiba Corporation

Apache Software Foundation, originally developed by HP

Initial release

2014

2006

2013

2014

Current release

5.0.1, July 2024

5.1, August 2022

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Apache 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

Scala

Python

C++

C++, Java

Server operating systems

Linux
Unix

Linux

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

HTTP API
Sockets

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Supported programming languages

JavaScript (Node.js)
Python

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

none

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

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

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

Time Series DBMS as a new trend?
1 June 2015, Paul Andlinger

show all

Recent citations in the news

Try out the Graphite monitoring tool for time-series data
29 October 2019, TechTarget

The Billion Data Point Challenge: Building a Query Engine for High Cardinality Time Series Data
10 December 2018, Uber

Getting Started with Monitoring using Graphite
23 January 2015, InfoQ.com

Most Prominent Time Series Databases For Data Scientists
6 September 2021, AIM

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

provided by Google News

TOSHIBA DIGITAL SOLUTIONS CORPORATION
1 November 2020, global.toshiba

Toshiba launches cloudy managed IoT database service running its own GridDB
8 April 2021, The Register

Now Features Scale-Out and Scale-Up combo for Petabyte-scale Data Management
3 December 2019, global.toshiba

Amazon Proposes to Develop New Data Center Campus in Virginia
26 August 2022, w.media

’s SQL Interface, Aims to Accelerate Open Innovation
17 June 2020, global.toshiba

provided by Google News

Share this page