DBMS > CouchDB vs. dBASE vs. Google BigQuery vs. HEAVY.AI

System Properties Comparison CouchDB vs. dBASE vs. Google BigQuery vs. HEAVY.AI

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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.

Large scale data warehouse service with append-only tables

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Primary database model

Document store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Spatial DBMS

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Website

couchdb.apache.org

www.dbase.com

cloud.google.com/bigquery

github.com/heavyai/heavydb
www.heavy.ai

Technical documentation

docs.couchdb.org/en/stable

www.dbase.com/support/knowledgebase

cloud.google.com/bigquery/docs

docs.heavy.ai

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Asthon Tate

Google

HEAVY.AI, Inc.

Initial release

2005

1979

2010

2016

Current release

3.3.3, December 2023

dBASE 2019, 2019

5.10, January 2022

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache Version 2; enterprise edition available

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

Erlang

C++ and CUDA

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

DOS

dBase Classic
Windows

dBase Pro

hosted

Linux

Data scheme

schema-free

yes

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

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

none

The IDE can access other DBMS or ODBC-sources.

RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

dBase proprietary IDE

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

View functions in JavaScript

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Multi-source replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

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

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

Access rights for users and roles

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

Google Cloud Identity & Access Management (IAM)

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.