DBMS > BigObject vs. Google Cloud Datastore vs. PouchDB vs. SQLite vs. Valentina Server

System Properties Comparison BigObject vs. Google Cloud Datastore vs. PouchDB vs. SQLite vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Object-relational database and reports server

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Relational DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

bigobject.io

cloud.google.com/datastore

pouchdb.com

www.sqlite.org

www.valentina-db.net

Technical documentation

docs.bigobject.io

cloud.google.com/datastore/docs

pouchdb.com/guides

www.sqlite.org/docs.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

BigObject, Inc.

Google

Apache Software Foundation

Dwayne Richard Hipp

Paradigma Software

Initial release

2015

2008

2012

2000

1999

Current release

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

5.7.5

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

Public Domain

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

JavaScript

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

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

server-less

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

not rigid because of 'dynamic typing' concept.

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

via views

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

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

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC

Supported programming languages

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

JavaScript

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

Lua

using Google App Engine

View functions in JavaScript

yes

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

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

automatically between fact table and dimension tables

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

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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 (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.