DBMS > Apache Doris vs. Microsoft Azure Cosmos DB vs. OrigoDB vs. Postgres-XL

System Properties Comparison Apache Doris vs. Microsoft Azure Cosmos DB vs. OrigoDB vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An MPP-based analytics DBMS embracing the MySQL protocol

Globally distributed, horizontally scalable, multi-model database service

A fully ACID in-memory object graph database

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.60
Rank	#247	Overall
	#113	Relational DBMS

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Website

doris.apache.org
github.com/apache/doris

azure.microsoft.com/services/cosmos-db

origodb.com

www.postgres-xl.org

Technical documentation

github.com/apache/doris/wiki

learn.microsoft.com/azure/cosmos-db

origodb.com/docs

www.postgres-xl.org/documentation

Developer

Apache Software Foundation, originally contributed from Baidu

Microsoft

Robert Friberg et al

Initial release

2017

2014

2009

under the name LiveDB

2014

since 2012, originally named StormDB

Current release

1.2.2, February 2023

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Mozilla public license

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

Java

Server operating systems

Linux

hosted

Linux
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

User defined using .NET types and collections

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.

can be achieved using .NET

yes

XML type, but no XML query functionality

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

JDBC
MySQL client

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

.NET Client API
HTTP API
LINQ

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

Supported programming languages

Java

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

.Net

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

JavaScript

yes

user defined functions

Triggers

JavaScript

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Implicit feature of the cloud service

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Access rights can be defined down to the item level

Role based authorization

fine grained access rights according to SQL-standard

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.