DBMS > Cubrid vs. Ignite vs. Microsoft Azure Cosmos DB vs. SWC-DB

System Properties Comparison Cubrid vs. Ignite vs. Microsoft Azure Cosmos DB vs. SWC-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

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.

Globally distributed, horizontally scalable, multi-model database service

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

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

ignite.apache.org

azure.microsoft.com/services/cosmos-db

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

cubrid.org/manuals

apacheignite.readme.io/docs

learn.microsoft.com/azure/cosmos-db

Developer

CUBRID Corporation, CUBRID Foundation

Apache Software Foundation

Microsoft

Alex Kashirin

Initial release

2008

2015

2014

2020

Current release

11.0, January 2021

Apache Ignite 2.6

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

Open Source

GPL V3

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

C++, Java, .Net

C++

Server operating systems

Linux
Windows

Linux
OS X
Solaris
Windows

hosted

Linux

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

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

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

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

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

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

Proprietary protocol
Thrift

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

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

C++

Server-side scripts

Stored procedures

Java Stored Procedures

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

JavaScript

Triggers

yes

yes (cache interceptors and events)

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes (replicated cache)

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

Immediate 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

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

User concepts

Access control

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

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.