DBMS > Firebase Realtime Database vs. IBM Cloudant vs. Microsoft SQL Server vs. OpenEdge

System Properties Comparison Firebase Realtime Database vs. IBM Cloudant vs. Microsoft SQL Server vs. OpenEdge

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Database as a Service offering based on Apache CouchDB

Microsofts flagship relational DBMS

Application development environment with integrated database management system

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

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

Website

firebase.google.com/products/realtime-database

www.ibm.com/products/cloudant

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

www.progress.com/openedge

Technical documentation

firebase.google.com/docs/database

cloud.ibm.com/docs/Cloudant

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

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Google

acquired by Google 2014

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Progress Software Corporation

Initial release

2012

2010

1989

1984

Current release

SQL Server 2022, November 2022

OpenEdge 12.2, March 2020

License

Commercial or Open Source

commercial

restricted free version is available

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

Erlang

C++

Server operating systems

hosted

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

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

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP/JSON API

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

JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

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)

Server-side scripts

Stored procedures

limited functionality with using 'rules'

View functions (Map-Reduce) in JavaScript

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

yes

Triggers

Callbacks are triggered when data changes

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

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

yes, based on authentication and database rules

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Users and groups

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.