DBMS > Couchbase vs. dBASE vs. Google Cloud Bigtable vs. Google Cloud Firestore vs. Rockset

System Properties Comparison Couchbase vs. dBASE vs. Google Cloud Bigtable vs. Google Cloud Firestore vs. Rockset

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Document store

Relational DBMS

Key-value store
Wide column store

Document store

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS
Search engine

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

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

www.couchbase.com

www.dbase.com

cloud.google.com/bigtable

firebase.google.com/products/firestore

rockset.com

Technical documentation

docs.couchbase.com

www.dbase.com/support/knowledgebase

cloud.google.com/bigtable/docs

firebase.google.com/docs/firestore

docs.rockset.com

Developer

Couchbase, Inc.

Asthon Tate

Google

Rockset

Initial release

2011

1979

2015

2017

2019

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

dBASE 2019, 2019

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

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

C, C++, Go and Erlang

C++

Server operating systems

Linux
OS X
Windows

DOS

dBase Classic
Windows

dBase Pro

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

Read-only SQL queries, including JOINs

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

none

The IDE can access other DBMS or ODBC-sources.

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

HTTP REST

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

dBase proprietary IDE

C#
C++
Go
Java
JavaScript (Node.js)
Python

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

The IDE can access stored procedures in other database systems.

yes, Firebase Rules & Cloud Functions

Triggers

yes

via the TAP protocol

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

Sharding

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

none

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Eventual 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

Atomic single-row operations

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

Ephemeral buckets

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Access rights for users and roles

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Access rights for users and organizations can be defined via Rockset console

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.