DBMS > Apache Drill vs. Atos Standard Common Repository vs. etcd vs. Google BigQuery vs. SiteWhere

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. etcd vs. Google BigQuery vs. SiteWhere

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

A distributed reliable key-value store

Large scale data warehouse service with append-only tables

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Key-value store

Relational DBMS

Time Series DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

drill.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

etcd.io
github.com/etcd-io/etcd

cloud.google.com/bigquery

github.com/sitewhere/sitewhere

Technical documentation

drill.apache.org/docs

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

cloud.google.com/bigquery/docs

sitewhere1.sitewhere.io/index.html

Developer

Apache Software Foundation

Atos Convergence Creators

Google

SiteWhere

Initial release

2012

2016

2010

Current release

1.20.3, January 2023

1703

3.4, August 2019

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2.0

commercial

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

Java

Server operating systems

Linux
OS X
Windows

Linux

FreeBSD
Linux
Windows

experimental

hosted

Linux
OS X
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

yes

predefined scheme

Typing

predefined data types such as float or date

yes

optional

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

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

gRPC
JSON over HTTP

RESTful HTTP/JSON API

HTTP REST

Supported programming languages

C++

All languages with LDAP bindings

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

LDAP bind authentication

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

Google Cloud Identity & Access Management (IAM)

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.