DBMS > Google Cloud Datastore vs. Graphite vs. Oracle vs. PouchDB

System Properties Comparison Google Cloud Datastore vs. Graphite vs. Oracle vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used RDBMS

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

cloud.google.com/datastore

github.com/graphite-project/graphite-web

www.oracle.com/database

pouchdb.com

Technical documentation

cloud.google.com/datastore/docs

graphite.readthedocs.io

docs.oracle.com/en/database

pouchdb.com/guides

Developer

Google

Chris Davis

Oracle

Apache Software Foundation

Initial release

2008

2006

1980

2012

Current release

23c, September 2023

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

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

Python

C and C++

JavaScript

Server operating systems

hosted

Linux
Unix

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

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

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes, details here

Numeric data only

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

via views

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

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

HTTP API
Sockets

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

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

JavaScript (Node.js)
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

JavaScript

Server-side scripts

Stored procedures

using Google App Engine

PL/SQL

also stored procedures in Java possible

View functions in JavaScript

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

none

Multi-source replication
Source-replica replication

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

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

locking

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

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

fine grained access rights according to SQL-standard

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.