DBMS > CockroachDB vs. Oracle Berkeley DB vs. Snowflake vs. SQream DB

System Properties Comparison CockroachDB vs. Oracle Berkeley DB vs. Snowflake vs. SQream DB

Please select another system to include it in the comparison.

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.

Widely used in-process key-value store

Cloud-based data warehousing service for structured and semi-structured data

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

www.cockroachlabs.com

www.oracle.com/database/technologies/related/berkeleydb.html

www.snowflake.com

sqream.com

Technical documentation

www.cockroachlabs.com/docs

docs.oracle.com/cd/E17076_05/html/index.html

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

Cockroach Labs

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

SQream Technologies

Initial release

2015

1994

2014

2017

Current release

23.1.1, May 2023

18.1.40, May 2020

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

commercial license available

commercial

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

C, Java, C++ (depending on the Berkeley DB edition)

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux
macOS
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

Linux

Data scheme

dynamic schema

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

JDBC

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

user defined functions in Python

Triggers

yes

only for the SQL API

similar concept for controling cloud resources

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

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Source-replica replication

yes

none

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

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, user roles and pluggable authentication

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.