DBMS > CockroachDB vs. Datomic vs. SAP SQL Anywhere vs. SQLite vs. Tibero

System Properties Comparison CockroachDB vs. Datomic vs. SAP SQL Anywhere vs. SQLite vs. Tibero

Editorial information provided by DB-Engines

Name

Description

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.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Widely used embeddable, in-process RDBMS

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Relational DBMS

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

www.cockroachlabs.com

www.datomic.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.sqlite.org

us.tmaxsoft.com/products/tibero

Technical documentation

www.cockroachlabs.com/docs

docs.datomic.com

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Cockroach Labs

Cognitect

SAP

formerly Sybase

Dwayne Richard Hipp

TmaxSoft

Initial release

2015

2012

1992

2000

2003

Current release

24.1.0, May 2024

1.0.6735, June 2023

17, July 2015

3.46.0 (23 May 2024), May 2024

6, April 2015

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

commercial

Open Source

Public Domain

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, Clojure

C and Assembler

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

dynamic schema

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC

RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

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

Clojure
Java

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

Transaction Functions

yes, in C/C++, Java, .Net or Perl

Persistent Stored Procedure (PSM)

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

But extensive use of caching in the application peers

none

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

none

But extensive use of caching in the application peers

Source-replica replication

Database mirroring

none

Multi-source 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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

planned for next version

User concepts

Access control

Role-based access control

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.