DBMS > BigchainDB vs. dBASE vs. Geode vs. Google BigQuery vs. PouchDB

System Properties Comparison BigchainDB vs. dBASE vs. Geode vs. Google BigQuery vs. PouchDB

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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Large scale data warehouse service with append-only tables

JavaScript DBMS with an API inspired by CouchDB

Primary database model

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

www.bigchaindb.com

www.dbase.com

geode.apache.org

cloud.google.com/bigquery

pouchdb.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

geode.apache.org/docs

cloud.google.com/bigquery/docs

pouchdb.com/guides

Developer

Asthon Tate

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

Apache Software Foundation

Initial release

2016

1979

2002

2010

2012

Current release

dBASE 2019, 2019

1.1, February 2017

7.1.1, June 2019

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

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

Python

Java

JavaScript

Server operating systems

Linux

DOS

dBase Classic
Windows

dBase Pro

All OS with a Java VM

the JDK (8 or later) is also required

hosted

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

Data scheme

schema-free

yes

schema-free

yes

schema-free

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

via views

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

dBase proprietary IDE

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

View functions in JavaScript

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

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, on a single node

Since BigQuery is designed for querying data

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

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

Access rights per client and object definable

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.