DBMS > Google BigQuery vs. SiteWhere vs. Yaacomo

System Properties Comparison Google BigQuery vs. SiteWhere vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Large scale data warehouse service with append-only tables

M2M integration platform for persisting/querying time series data

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

cloud.google.com/bigquery

github.com/sitewhere/sitewhere

yaacomo.com

Technical documentation

cloud.google.com/bigquery/docs

sitewhere1.sitewhere.io/index.html

Developer

Google

SiteWhere

Q2WEB GmbH

Initial release

2010

2009

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.0

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

Java

Server operating systems

hosted

Linux
OS X
Windows

Android
Linux
Windows

Data scheme

yes

predefined scheme

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP REST

JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on HBase

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

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)

Users with fine-grained authorization concept

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.