DBMS > Couchbase vs. Firebase Realtime Database vs. Google Cloud Datastore vs. Graphite

System Properties Comparison Couchbase vs. Firebase Realtime Database vs. Google Cloud Datastore vs. Graphite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Primary database model

Document store

Time Series DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Website

www.couchbase.com

firebase.google.com/products/realtime-database

cloud.google.com/datastore

github.com/graphite-project/graphite-web

Technical documentation

docs.couchbase.com

firebase.google.com/docs/database

cloud.google.com/datastore/docs

graphite.readthedocs.io

Developer

Couchbase, Inc.

Google

acquired by Google 2014

Google

Chris Davis

Initial release

2011

2012

2008

2006

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also 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.

Implementation language

C, C++, Go and Erlang

Python

Server operating systems

Linux
OS X
Windows

hosted

Linux
Unix

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

Numeric data only

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.

Secondary indexes

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

SQL-like query language (GQL)

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

Android
iOS
JavaScript API
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP API
Sockets

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Java
JavaScript
Objective-C

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

limited functionality with using 'rules'

using Google App Engine

Triggers

yes

via the TAP protocol

Callbacks are triggered when data changes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

none

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

locking

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

Ephemeral buckets

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

yes, based on authentication and database rules

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.