DBMS > Badger vs. CockroachDB vs. dBASE vs. RocksDB vs. SiteWhere

System Properties Comparison Badger vs. CockroachDB vs. dBASE vs. RocksDB vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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.

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

M2M integration platform for persisting/querying time series data

Primary database model

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

github.com/dgraph-io/badger

www.cockroachlabs.com

www.dbase.com

rocksdb.org

github.com/sitewhere/sitewhere

Technical documentation

godoc.org/github.com/dgraph-io/badger

www.cockroachlabs.com/docs

www.dbase.com/support/knowledgebase

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

Developer

DGraph Labs

Cockroach Labs

Asthon Tate

Facebook, Inc.

SiteWhere

Initial release

2017

2015

1979

2013

2010

Current release

23.1.1, May 2023

dBASE 2019, 2019

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0, commercial license available

commercial

Open Source

BSD

Open Source

Common Public Attribution License Version 1.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

C++

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

DOS

dBase Classic
Windows

dBase Pro

Linux

Linux
OS X
Windows

Data scheme

schema-free

dynamic schema

yes

schema-free

predefined scheme

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.

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

APIs and other access methods

JDBC

none

The IDE can access other DBMS or ODBC-sources.

C++ API
Java API

HTTP REST

Supported programming languages

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

dBase proprietary IDE

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

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

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using RAFT

none

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

not for dBase internal data, but IDE does support transactions when accessing external DBMS

yes

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

Access rights for users and roles

Users with fine-grained authorization concept

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.