DBMS > Atos Standard Common Repository vs. Google BigQuery vs. Heroic vs. Kdb vs. SwayDB

System Properties Comparison Atos Standard Common Repository vs. Google BigQuery vs. Heroic vs. Kdb vs. SwayDB

Editorial information provided by DB-Engines

Name

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

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

High performance Time Series DBMS

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

Time Series DBMS
Vector DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	7.71
Rank	#49	Overall
	#2	Time Series DBMS
	#1	Vector DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

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

cloud.google.com/bigquery

github.com/spotify/heroic

kx.com

swaydb.simer.au

Technical documentation

cloud.google.com/bigquery/docs

spotify.github.io/heroic

code.kx.com

Developer

Atos Convergence Creators

Google

Spotify

Kx Systems, a division of First Derivatives plc

Simer Plaha

Initial release

2016

2010

2014

2000

kdb was released 2000, kdb+ in 2003

2018

Current release

1703

3.6, May 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free 32-bit version

Open Source

GNU Affero GPL V3.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

Scala

Server operating systems

Linux

hosted

Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

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

via Elasticsearch

yes

table attribute 'grouped'

SQL

Support of SQL

yes

SQL-like query language (q)

APIs and other access methods

LDAP

RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

Supported programming languages

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Triggers

yes

with views

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

similar paradigm used for internal processing

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency
Immediate Consistency

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

Since BigQuery is designed for querying data

Atomic execution of operations

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

LDAP bind authentication

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

Google Cloud Identity & Access Management (IAM)

rights management via user accounts

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

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.