DBMS > Google BigQuery vs. GridDB vs. PouchDB vs. Sphinx

System Properties Comparison Google BigQuery vs. GridDB vs. PouchDB vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Scalable in-memory time series database optimized for IoT and Big Data

JavaScript DBMS with an API inspired by CouchDB

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Secondary database models

Key-value store
Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

cloud.google.com/bigquery

griddb.net

pouchdb.com

sphinxsearch.com

Technical documentation

cloud.google.com/bigquery/docs

docs.griddb.net

pouchdb.com/guides

sphinxsearch.com/docs

Developer

Google

Toshiba Corporation

Apache Software Foundation

Sphinx Technologies Inc.

Initial release

2010

2013

2012

2001

Current release

5.1, August 2022

7.1.1, June 2019

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

GPL version 2, commercial licence available

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++

JavaScript

C++

Server operating systems

hosted

Linux

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

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

full-text index on all search fields

SQL

Support of SQL

yes

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

ACID at container level

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

The original contents of fields are not stored in the Sphinx index.

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users can be defined per database

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.