DBMS > Google BigQuery vs. Graphite vs. GridDB vs. searchxml

System Properties Comparison Google BigQuery vs. Graphite vs. GridDB vs. searchxml

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

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

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Time Series DBMS

Native XML DBMS
Search engine

Secondary database models

Key-value store
Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

cloud.google.com/bigquery

github.com/graphite-project/graphite-web

griddb.net

www.searchxml.net/category/products

Technical documentation

cloud.google.com/bigquery/docs

graphite.readthedocs.io

docs.griddb.net

www.searchxml.net/support/handouts

Developer

Google

Chris Davis

Toshiba Corporation

informationpartners gmbh

Initial release

2010

2006

2013

2015

Current release

5.1, August 2022

1.0

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

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

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

Python

C++

Server operating systems

hosted

Linux
Unix

Linux

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL

Support of SQL

yes

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Sockets

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript (Node.js)
Python

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

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

sychronisation to multiple collections

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate consistency within container, eventual consistency across containers

Immediate 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

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

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

Domain, group and role-based access control at the document level and for application services

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.