DBMS > Badger vs. Google Cloud Datastore vs. jBASE vs. PouchDB

System Properties Comparison Badger vs. Google Cloud Datastore vs. jBASE vs. PouchDB

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.

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

A robust multi-value DBMS comprising development tools and middleware

JavaScript DBMS with an API inspired by CouchDB

Primary database model

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

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

github.com/dgraph-io/badger

cloud.google.com/datastore

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

pouchdb.com

Technical documentation

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

cloud.google.com/datastore/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

pouchdb.com/guides

Developer

DGraph Labs

Google

Rocket Software (formerly Zumasys)

Apache Software Foundation

Initial release

2017

2008

1991

2012

Current release

5.7

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

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

JavaScript

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

AIX
Linux
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

schema-free

Typing

predefined data types such as float or date

yes, details here

optional

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

via views

SQL

Support of SQL

SQL-like query language (GQL)

Embedded SQL for jBASE in BASIC

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

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

.Net
Basic
Jabbascript
Java

JavaScript

Server-side scripts

Stored procedures

using Google App Engine

yes

View functions in JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

yes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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.

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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 (IAM)

Access rights can be defined down to the item level

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

New kids on the block: database management systems implemented in JavaScript
1 December 2014, Matthias Gelbmann

show all

Recent citations in the news

Best cloud storage of 2024
21 May 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google Cloud is NOT magicking away data egress fees
12 January 2024, The Stack

Why Google is waiving egress fees for disgruntled customers ditching GCP
11 January 2024, The Register

provided by Google News

Building an Offline First App with PouchDB — SitePoint
10 March 2014, SitePoint

Getting Started with PouchDB Client-Side JavaScript Database — SitePoint
7 September 2016, SitePoint

3 Reasons To Think Offline First
22 March 2017, ibm.com

Create Offline Web Apps Using Service Workers & PouchDB — SitePoint
7 March 2017, SitePoint

Offline-first web and mobile apps: Top frameworks and components
22 January 2019, TechBeacon

provided by Google News

Share this page