DBMS > Atos Standard Common Repository vs. CockroachDB vs. Drizzle vs. Linter

System Properties Comparison Atos Standard Common Repository vs. CockroachDB vs. Drizzle vs. Linter

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

RDBMS for high security requirements

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	0.03
Rank	#368	Overall
	#156	Relational DBMS

Website

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

www.cockroachlabs.com

linter.ru

Technical documentation

www.cockroachlabs.com/docs

Developer

Atos Convergence Creators

Cockroach Labs

Drizzle project, originally started by Brian Aker

relex.ru

Initial release

2016

2015

2008

1990

Current release

1703

24.1.0, May 2024

7.2.4, September 2012

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

Open Source

GNU GPL

commercial

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++

Server operating systems

Linux

Linux
macOS
Windows

FreeBSD
Linux
OS X

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Data scheme

Schema and schema-less with LDAP views

dynamic schema

yes

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, wire compatible with PostgreSQL

yes

with proprietary extensions

yes

APIs and other access methods

LDAP

JDBC

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

All languages with LDAP bindings

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

C
C++
Java
PHP

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

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

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

Source-replica replication

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

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

Role-based access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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

Cockroach Labs shakes up its licensing to force bigger companies to pay
15 August 2024, TechCrunch

CockroachDB scuttles away from open source Core offering
19 August 2024, The Register

CockroachDB retires self-hosted Core offering, makes Enterprise version free for companies under $10M in annual revenue
15 August 2024, SDTimes.com

Cockroach Labs Deepens Partnership with Google Cloud, CockroachDB Selected to Join Google Distributed Cloud
9 April 2024, PR Newswire

DoorDash Uses CockroachDB to Create Config Management Platform for Microservices
14 February 2024, InfoQ.com

provided by Google News

Share this page