DBMS > Cubrid vs. FatDB vs. PostGIS vs. STSdb

System Properties Comparison Cubrid vs. FatDB vs. PostGIS vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Spatial extension of PostgreSQL

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Document store
Key-value store

Spatial DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

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

postgis.net

github.com/STSSoft/STSdb4

Technical documentation

cubrid.org/manuals

postgis.net/documentation

Developer

CUBRID Corporation, CUBRID Foundation

FatCloud

STS Soft SC

Initial release

2008

2012

2005

2011

Current release

11.0, January 2021

3.4.2, February 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL v2.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

Server operating systems

Linux
Windows

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

.NET Client API

Supported programming languages

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

C#
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via applications

user defined functions

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

based on PostgreSQL

none

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
Immediate Consistency

Immediate 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

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

yes

based on PostgreSQL

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.