DBMS > IBM Cloudant vs. Microsoft SQL Server vs. OpenEdge vs. YugabyteDB

System Properties Comparison IBM Cloudant vs. Microsoft SQL Server vs. OpenEdge vs. YugabyteDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Microsofts flagship relational DBMS

Application development environment with integrated database management system

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Wide column store

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	2.91
Rank	#102	Overall
	#51	Relational DBMS

Website

www.ibm.com/products/cloudant

www.microsoft.com/en-us/sql-server

www.progress.com/openedge

www.yugabyte.com

Technical documentation

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/en-US/sql/sql-server

documentation.progress.com/output/ua/OpenEdge_latest

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Progress Software Corporation

Yugabyte Inc.

Initial release

2010

1989

1984

2017

Current release

SQL Server 2022, November 2022

OpenEdge 12.2, March 2020

2.19, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

Apache 2.0

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.

YugabyteDB Managed is the fully managed database-as-a-service offering of YugabyteDB. Get started quickly, and effortlessly ensure continuous availability and limitless scale of your cloud native applications.

Implementation language

Erlang

C++

C and C++

Server operating systems

hosted

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

Data scheme

schema-free

yes

depending on used data model

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes, PostgreSQL compatible

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

JDBC
ODBC

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Progress proprietary ABL (Advanced Business Language)

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

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

sql, plpgsql, C

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

horizontal partitioning

since Version 11.4

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

Source-replica replication

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Strong consistency on writes and tunable consistency on reads

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

based on RocksDB

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Users and groups

yes

More information provided by the system vendor

Specific characteristics

YugabyteDB is an open source distributed SQL database for cloud native transactional...
» more

Competitive advantages

PostgreSQL compatible: Get instantly productive with a PostgreSQL compatible RDBMS....
» more

Typical application scenarios

Systems of record and engagement for cloud native applications that require resilience,...
» more

Market metrics

2 Million+ lifetime clusters deployed, 6.5K+ GitHub stars, 7K YugabyteDB Community...
» more

Licensing and pricing models

Apache 2.0 license for the database
» more

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.