DBMS > dBASE vs. Google BigQuery vs. Google Cloud Datastore vs. RDF4J vs. Splice Machine

System Properties Comparison dBASE vs. Google BigQuery vs. Google Cloud Datastore vs. RDF4J vs. Splice Machine

Editorial information provided by DB-Engines

Name

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.

Large scale data warehouse service with append-only tables

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

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	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

www.dbase.com

cloud.google.com/bigquery

cloud.google.com/datastore

rdf4j.org

splicemachine.com

Technical documentation

www.dbase.com/support/knowledgebase

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

rdf4j.org/documentation

splicemachine.com/how-it-works

Developer

Asthon Tate

Google

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Splice Machine

Initial release

1979

2010

2008

2004

2014

Current release

dBASE 2019, 2019

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

AGPL 3.0, commercial license 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

Java

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

hosted

Linux
OS X
Unix
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

yes

SQL-like query language (GQL)

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
Native Spark Datasource
ODBC

Supported programming languages

dBase proprietary IDE

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
PHP
Python

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

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

using Google App Engine

yes

Java

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

Since BigQuery is designed for querying data

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

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

Google Cloud Identity & Access Management (IAM)

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

Access rights for users, groups and roles 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.