DBMS > CockroachDB vs. EventStoreDB vs. HarperDB vs. Oracle

System Properties Comparison CockroachDB vs. EventStoreDB vs. HarperDB vs. Oracle

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.

Industrial-strength, open-source database solution built from the ground up for event sourcing.

HarperDB takes the "stack" out of "tech stack" by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and your application components into a single distributed technology.

Widely used RDBMS

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	1.07
Rank	#181	Overall
	#1	Event Stores

Score	0.55
Rank	#243	Overall
	#38	Document stores

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Website

www.cockroachlabs.com

www.eventstore.com

www.harperdb.io

www.oracle.com/database

Technical documentation

www.cockroachlabs.com/docs

developers.eventstore.com

docs.harperdb.io/docs

docs.oracle.com/en/database

Developer

Cockroach Labs

Event Store Limited

HarperDB

Oracle

Initial release

2015

2012

2017

1980

Current release

24.1.0, May 2024

21.2, February 2021

3.1, August 2021

23c, September 2023

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

commercial

free community edition available

commercial

restricted free version is available

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

Node.js

C and C++

Server operating systems

Linux
macOS
Windows

Linux
Windows

Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

dynamic schema

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL-like data manipulation statements

yes

with proprietary extensions

APIs and other access methods

JDBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

PL/SQL

also stored procedures in Java possible

Triggers

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

A table resides as a whole on one (or more) nodes in a cluster

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

yes

the nodes on which a table resides can be defined

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

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

Atomic execution of specific operations

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

In-memory capabilities

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

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Role-based access control

Access rights for users and 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.