DBMS > Cubrid vs. Geode vs. GeoMesa vs. Kinetica

System Properties Comparison Cubrid vs. Geode vs. GeoMesa vs. Kinetica

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

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

Fully vectorized database across both GPUs and CPUs

Primary database model

Secondary database models

Spatial 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.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Website

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

geode.apache.org

www.geomesa.org

www.kinetica.com

Technical documentation

cubrid.org/manuals

geode.apache.org/docs

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

docs.kinetica.com

Developer

CUBRID Corporation, CUBRID Foundation

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

CCRi and others

Kinetica

Initial release

2008

2002

2014

2012

Current release

11.0, January 2021

1.1, February 2017

4.0.5, February 2024

7.1, August 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache License 2.0

commercial

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

Java

Scala

C, C++

Server operating systems

Linux
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

Supported programming languages

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

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

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

depending on storage layer

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

depending on storage layer

Immediate Consistency or Eventual Consistency depending on configuration

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

depending on storage layer

yes

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

yes

depending on the DBMS used for storage

Access rights for users and roles on table level

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

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

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Kinetica Elevates RAG with Fast Access to Real-Time Data
26 March 2024, Datanami

Kinetica Delivers Real-Time Vector Similarity Search
21 March 2024, insideBIGDATA

Kinetica ramps up RAG for generative AI, empowering enterprises with real-time operational data
18 March 2024, SiliconANGLE News

Kinetica Launches Generative AI Solution for Real-Time Inferencing Powered by NVIDIA AI Enterprise
18 March 2024, GlobeNewswire

Transforming spatiotemporal data analysis with GPUs and generative AI
30 October 2023, InfoWorld

provided by Google News

Share this page