DBMS > atoti vs. CockroachDB vs. MySQL vs. Trafodion

System Properties Comparison atoti vs. CockroachDB vs. MySQL vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

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.

Widely used open source RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Object oriented DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.45
Rank	#253	Overall
	#13	Object oriented DBMS

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

atoti.io

www.cockroachlabs.com

www.mysql.com

trafodion.apache.org

Technical documentation

docs.atoti.io

www.cockroachlabs.com/docs

dev.mysql.com/doc

trafodion.apache.org/documentation.html

Developer

ActiveViam

Cockroach Labs

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation, originally developed by HP

Initial release

2015

1995

2014

Current release

24.1.0, May 2024

9.0.0, July 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

free versions available

Open Source

Apache 2.0, commercial license available

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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 and C++

C++, Java

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

dynamic schema

yes

Typing

predefined data types such as float or date

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

Multidimensional Expressions (MDX)

yes, wire compatible with PostgreSQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Python

yes

proprietary syntax

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

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

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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.