DBMS > BigchainDB vs. dBASE vs. PouchDB vs. RocksDB vs. XTDB

System Properties Comparison BigchainDB vs. dBASE vs. PouchDB vs. RocksDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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.

JavaScript DBMS with an API inspired by CouchDB

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

www.xtdb.com/docs

Developer

Asthon Tate

Apache Software Foundation

Facebook, Inc.

Juxt Ltd.

Initial release

2016

1979

2012

2013

2019

Current release

dBASE 2019, 2019

7.1.1, June 2019

9.2.1, May 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

BSD

Open Source

MIT License

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

Python

JavaScript

C++

Clojure

Server operating systems

Linux

DOS

dBase Classic
Windows

dBase Pro

server-less, requires a JavaScript environment (browser, Node.js)

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

via views

yes

SQL

Support of SQL

limited SQL, making use of Apache Calcite

APIs and other access methods

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

HTTP REST
JDBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

dBase proprietary IDE

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

yes

Access rights for users and roles

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.