DBMS > Cubrid vs. GBase vs. GeoMesa vs. Ignite vs. Prometheus

System Properties Comparison Cubrid vs. GBase vs. GeoMesa vs. Ignite vs. Prometheus

Editorial information provided by DB-Engines

Name

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

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.

Open-source Time Series DBMS and monitoring system

Primary database model

Relational DBMS

Spatial DBMS

Key-value store
Relational DBMS

Time Series DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

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

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

cubrid.com (korean)
cubrid.org (english)

Technical documentation

cubrid.org/manuals

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

apacheignite.readme.io/docs

prometheus.io/docs

Developer

CUBRID Corporation, CUBRID Foundation

General Data Technology Co., Ltd.

CCRi and others

Apache Software Foundation

Initial release

2008

2004

2014

2015

Current release

11.0, January 2021

GBase 8a, GBase 8s, GBase 8c

4.0.5, February 2024

Apache Ignite 2.6

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

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

C, C++, Java

C, Java, Python

Scala

C++, Java, .Net

Server operating systems

Linux
Windows

Linux

Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

Standard with numerous extensions

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

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
C API
JDBC
ODBC

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

RESTful HTTP/JSON API

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

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

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

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

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

depending on storage layer

yes (replicated cache)

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

none

Foreign keys

Referential integrity

yes

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

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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Security Hooks for custom implementations

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

Recent citations in the news

Apache Ignite: An Overview
6 September 2023, Open Source For You

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

Fire up big data processing with Apache Ignite
27 October 2016, InfoWorld

provided by Google News

VTEX scales to 150 million metrics using Amazon Managed Service for Prometheus | Amazon Web Services
10 March 2024, AWS Blog

VictoriaMetrics Offers Prometheus Replacement for Time Series Monitoring
17 July 2023, The New Stack

Linux System Monitoring with Prometheus, Grafana, and collectd
1 February 2024, Linux Journal

Consider Grafana vs. Prometheus for your time-series tools
18 October 2021, TechTarget

How to reduce Istio sidecar metric cardinality with Amazon Managed Service for Prometheus | Amazon Web Services
10 October 2023, AWS Blog

provided by Google News

Share this page