DBMS > Apache IoTDB vs. EsgynDB vs. GBase vs. Geode

System Properties Comparison Apache IoTDB vs. EsgynDB vs. GBase vs. Geode

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Primary database model

Time Series DBMS

Relational DBMS

Key-value store

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

Score	1.31
Rank	#159	Overall
	#14	Time Series DBMS

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	1.11
Rank	#173	Overall
	#78	Relational DBMS

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Website

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

geode.apache.org/docs

Developer

Apache Software Foundation

Esgyn

General Data Technology Co., Ltd.

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Initial release

2018

2015

2004

2002

Current release

1.1.0, April 2023

GBase 8a, GBase 8s, GBase 8c

1.1, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

C++, Java

C, Java, Python

Java

Server operating systems

All OS with a Java VM (>= 1.8)

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Data scheme

yes

schema-free

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

SQL-like query language

yes

Standard with numerous extensions

SQL-like query language (OQL)

APIs and other access methods

JDBC
Native API

ADO.NET
JDBC
ODBC

ADO.NET
C API
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

All languages supporting JDBC/ODBC/ADO.Net

.Net
All JVM based languages
C++
Groovy
Java
Scala

Server-side scripts

Stored procedures

yes

Java Stored Procedures

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

Multi-source replication between multi datacenters

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

Concurrency

Support for concurrent manipulation of data

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.

yes

User concepts

Access control

yes

fine grained access rights according to SQL-standard

yes

Access rights per client and object definable

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

Recent citations in the news

AMD Zen 5 Not Affected By Inception/SRSO, mitigations=off Yields No Benefit On Ryzen 9000 Series
6 September 2024, Phoronix

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

AMD EPYC 8534P / EPYC 8534PN Benchmarks - Siena Delivers Incredible Value & Energy Efficiency For Linux Servers Review
29 November 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

IoTDB Provides Data Management for Industrial Edge IT
15 October 2020, The New Stack

provided by Google News

RDBMS and Apache Geode Data Movement: Low Latency ETL Pipeline by Using Cloud-Native Event Driven Microservices
30 June 2018, InfoQ.com

Chapter 1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode
15 November 2018, O'Reilly Media

HPE buys query acceleration platform Ampool to boost Ezmeral hybrid cloud analytics
7 July 2021, SiliconANGLE News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

HPE acquires Ampool to gain distributed SQL engine
9 July 2021, VentureBeat

provided by Google News

Share this page