DBMS > Badger vs. Google Cloud Firestore vs. HugeGraph vs. IBM Cloudant

System Properties Comparison Badger vs. Google Cloud Firestore vs. HugeGraph vs. IBM Cloudant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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.

A fast-speed and highly-scalable Graph DBMS

Database as a Service offering based on Apache CouchDB

Primary database model

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Website

github.com/dgraph-io/badger

firebase.google.com/products/firestore

github.com/hugegraph
hugegraph.apache.org

www.ibm.com/products/cloudant

Technical documentation

godoc.org/github.com/dgraph-io/badger

firebase.google.com/docs/firestore

hugegraph.apache.org/docs

cloud.ibm.com/docs/Cloudant

Developer

DGraph Labs

Google

Baidu

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2017

2018

2010

Current release

0.9

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

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

Java

Erlang

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux
macOS
Unix

hosted

Data scheme

schema-free

yes

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.

Secondary indexes

yes

also supports composite index and range index

yes

SQL

Support of SQL

APIs and other access methods

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

Java API
RESTful HTTP API
TinkerPop Gremlin

RESTful HTTP/JSON API

Supported programming languages

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

Groovy
Java
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

asynchronous Gremlin script jobs

View functions (Map-Reduce) in JavaScript

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

depending on used storage backend, e.g. Cassandra and HBase

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

via hugegraph-spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

edges in graph

Transaction concepts

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

yes

ACID

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic 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

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.

Users, roles and permissions

Access rights for users can be defined per database

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

Critical Apache HugeGraph Flaw Let Attackers Execute Remote Code
23 April 2024, GBHackers

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