DBMS > Cubrid vs. GeoMesa vs. NSDb vs. STSdb

System Properties Comparison Cubrid vs. GeoMesa vs. NSDb vs. STSdb

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

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

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

www.geomesa.org

nsdb.io

github.com/STSSoft/STSdb4

Technical documentation

cubrid.org/manuals

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

nsdb.io/Architecture

Developer

CUBRID Corporation, CUBRID Foundation

CCRi and others

STS Soft SC

Initial release

2008

2014

2017

2011

Current release

11.0, January 2021

5.0.0, May 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

Open Source

GPLv2, commercial license available

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

Scala

Java, Scala

Server operating systems

Linux
Windows

Linux
macOS

Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

yes

primitive types and user defined types (classes)

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

all fields are automatically indexed

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

gRPC
HTTP REST
WebSocket

.NET Client API

Supported programming languages

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

Java
Scala

C#
Java

Server-side scripts

Stored procedures

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency

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

Using Apache Lucene

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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.