DBMS > Google Cloud Firestore vs. IBM Cloudant vs. OpenQM vs. searchxml

System Properties Comparison Google Cloud Firestore vs. IBM Cloudant vs. OpenQM vs. searchxml

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Database as a Service offering based on Apache CouchDB

QpenQM is a high-performance, self-tuning, multi-value DBMS

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store

Multivalue DBMS

Native XML DBMS
Search engine

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

firebase.google.com/products/firestore

www.ibm.com/products/cloudant

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.searchxml.net/category/products

Technical documentation

firebase.google.com/docs/firestore

cloud.ibm.com/docs/Cloudant

www.searchxml.net/support/handouts

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Rocket Software, originally Martin Phillips

informationpartners gmbh

Initial release

2017

2010

1993

2015

Current release

3.4-12

1.0

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license 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

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Windows

Data scheme

schema-free

yes

with some exceptions

schema-free

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

APIs and other access methods

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP/JSON API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
Basic
C
Java
Objective C
PHP
Python

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

View functions (Map-Reduce) in JavaScript

yes

on the application server

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

atomic operations within a document possible

ACID

multiple readers, single writer

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.

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Access rights for users can be defined per database

Access rights can be defined down to the item level

Domain, group and role-based access control at the document level and for application services

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google’s Firebase gets AI extensions, opens up its marketplace
10 May 2023, TechCrunch

Google's Cloud Firestore is now generally available
31 January 2019, ZDNet

Firestore and Python | NoSQL on Google Cloud
7 August 2020, Towards Data Science

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, ibm.com

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, ibm.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

Share this page