DBMS > dBASE vs. FatDB vs. Google BigQuery vs. Splice Machine vs. VoltDB

System Properties Comparison dBASE vs. FatDB vs. Google BigQuery vs. Splice Machine vs. VoltDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Large scale data warehouse service with append-only tables

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.dbase.com

cloud.google.com/bigquery

splicemachine.com

www.voltdb.com

Technical documentation

www.dbase.com/support/knowledgebase

cloud.google.com/bigquery/docs

splicemachine.com/how-it-works

docs.voltdb.com

Developer

Asthon Tate

FatCloud

Google

Splice Machine

VoltDB Inc.

Initial release

1979

2012

2010

2014

2010

Current release

dBASE 2019, 2019

3.1, March 2021

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

AGPL 3.0, commercial license available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java

Java, C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

Windows

hosted

Linux
OS X
Solaris
Windows

Linux
OS X

for development

Data scheme

yes

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

SQL

Support of SQL

Via inetgration in SQL Server

yes

only a subset of SQL 99

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

JDBC
Native Spark Datasource
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

dBase proprietary IDE

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

via applications

user defined functions

in JavaScript

yes

Java

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

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

Since BigQuery is designed for querying data

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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 and roles

Can implement custom security layer via applications

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

Google Cloud Identity & Access Management (IAM)

Access rights for users, groups and roles according to SQL-standard

Users and roles with access to stored procedures

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.