DBMS > Apache Drill vs. Atos Standard Common Repository vs. Google BigQuery vs. NSDb vs. SWC-DB

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. Google BigQuery vs. NSDb vs. SWC-DB

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

Large scale data warehouse service with append-only tables

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A high performance, scalable Wide Column DBMS

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Relational DBMS

Time Series DBMS

Wide column store

Secondary database models

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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

drill.apache.org

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

cloud.google.com/bigquery

nsdb.io

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

drill.apache.org/docs

cloud.google.com/bigquery/docs

nsdb.io/Architecture

Developer

Apache Software Foundation

Atos Convergence Creators

Google

Alex Kashirin

Initial release

2012

2016

2010

2017

2020

Current release

1.20.3, January 2023

1703

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2.0

Open Source

GPL V3

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

Java, Scala

C++

Server operating systems

Linux
OS X
Windows

Linux

hosted

Linux
macOS

Linux

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

RESTful HTTP/JSON API

gRPC
HTTP REST
WebSocket

Proprietary protocol
Thrift

Supported programming languages

C++

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Scala

C++

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Eventual Consistency

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

Using Apache Lucene

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)

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.