DBMS > Atos Standard Common Repository vs. Drizzle vs. IBM Db2 vs. KairosDB

System Properties Comparison Atos Standard Common Repository vs. Drizzle vs. IBM Db2 vs. KairosDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Common in IBM host environments, 2 different versions for host and Windows/Linux

Distributed Time Series DBMS based on Cassandra or H2

Primary database model

Document store
Key-value store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Time Series DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Website

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

www.ibm.com/products/db2

github.com/kairosdb/kairosdb

Technical documentation

www.ibm.com/docs/en/db2

kairosdb.github.io

Developer

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

IBM

Initial release

2016

2008

1983

host version

2013

Current release

1703

7.2.4, September 2012

12.1, October 2016

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

free version is available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

C and C++

Java

Server operating systems

Linux

FreeBSD
Linux
OS X

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

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

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

LDAP

JDBC

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

All languages with LDAP bindings

C
C++
Java
PHP

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

only with Windows/Unix/Linux Version

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

with separate tools (MQ, InfoSphere)

selectable replication factor

based on Cassandra

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

simple password-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

Expo: Real Time A/B Testing and Monitoring with Spark Streaming and Kafka at Walmart Labs
24 May 2019, InfoQ.com

provided by Google News

Share this page