DBMS > Google BigQuery vs. Graphite vs. MaxDB vs. SiteWhere

System Properties Comparison Google BigQuery vs. Graphite vs. MaxDB 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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

A robust and reliable RDBMS optimized to run all major SAP solutions

M2M integration platform for persisting/querying time series data

Primary database model

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.26
Rank	#114	Overall
	#55	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

cloud.google.com/bigquery

github.com/graphite-project/graphite-web

maxdb.sap.com

github.com/sitewhere/sitewhere

Technical documentation

cloud.google.com/bigquery/docs

graphite.readthedocs.io

maxdb.sap.com/documentation

sitewhere1.sitewhere.io/index.html

Developer

Google

Chris Davis

SAP, acquired from Software AG (Adabas-D) in 1997

SiteWhere

Initial release

2010

2006

1984

2010

Current release

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Limited community edition free

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

Python

C++

Java

Server operating systems

hosted

Linux
Unix

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

predefined scheme

Typing

predefined data types such as float or date

yes

Numeric data only

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

ADO.NET
JDBC
ODBC
WebDAV

HTTP REST

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript (Node.js)
Python

.Net
C#
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

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.

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.