DBMS > Cubrid vs. EDB Postgres vs. Microsoft Azure Cosmos DB

System Properties Comparison Cubrid vs. EDB Postgres vs. Microsoft Azure Cosmos DB

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

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

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

www.enterprisedb.com

azure.microsoft.com/services/cosmos-db

Technical documentation

cubrid.org/manuals

www.enterprisedb.com/docs

learn.microsoft.com/azure/cosmos-db

Developer

CUBRID Corporation, CUBRID Foundation

EnterpriseDB

Microsoft

Initial release

2008

2005

2014

Current release

11.0, January 2021

14, December 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

BSD for PostgreSQL-components

commercial

Cloud-based only

Only available as a cloud service

yes

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

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

standard with numerous extensions

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

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

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

by hash, list or range

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Access rights can be defined down to the item 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.