DBMS > Google BigQuery vs. GridDB vs. OrigoDB vs. SiteWhere

System Properties Comparison Google BigQuery vs. GridDB vs. OrigoDB vs. SiteWhere

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

A fully ACID in-memory object graph database

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Time Series DBMS

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	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

cloud.google.com/bigquery

griddb.net

origodb.com

github.com/sitewhere/sitewhere

Technical documentation

cloud.google.com/bigquery/docs

docs.griddb.net

origodb.com/docs

sitewhere1.sitewhere.io/index.html

Developer

Google

Toshiba Corporation

Robert Friberg et al

SiteWhere

Initial release

2010

2013

2009

under the name LiveDB

2010

Current release

5.1, August 2022

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

Common Public Attribution License Version 1.0

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

Java

Server operating systems

hosted

Linux

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

predefined scheme

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

HTTP REST

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on HBase

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

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

Since BigQuery is designed for querying data

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

Users with fine-grained authorization concept

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.