DBMS > Atos Standard Common Repository vs. BigchainDB vs. QuestDB vs. Snowflake vs. Yanza

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. QuestDB vs. Snowflake vs. Yanza

Editorial information provided by DB-Engines

Name

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

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

A high performance open source SQL database for time series data

Cloud-based data warehousing service for structured and semi-structured data

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

Secondary database models

Relational DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.bigchaindb.com

questdb.io

www.snowflake.com

yanza.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

questdb.io/docs

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

QuestDB Technology Inc

Snowflake Computing Inc.

Yanza

Initial release

2016

2014

2015

Current release

1703

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Python

Java (Zero-GC), C++, Rust

Server operating systems

Linux

Linux
macOS
Windows

hosted

Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free via InfluxDB Line Protocol

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

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 with time-series extensions

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

JavaScript (Node.js)
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning (by timestamps)

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication with eventual consistency

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID for single-table writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

yes

through memory mapped files

User concepts

Access control

LDAP bind authentication

yes

Users with fine-grained authorization concept, user roles and pluggable authentication

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

Create an IoT server with QuestDB and a Raspberry Pi
4 April 2024

TimescaleDB vs. QuestDB: Performance benchmarks and overview
27 March 2024

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.