DBMS > dBASE vs. Google BigQuery vs. Oracle NoSQL vs. Splice Machine vs. Tarantool

System Properties Comparison dBASE vs. Google BigQuery vs. Oracle NoSQL vs. Splice Machine vs. Tarantool

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

www.dbase.com

cloud.google.com/bigquery

www.oracle.com/database/nosql/technologies/nosql

splicemachine.com

www.tarantool.io

Technical documentation

www.dbase.com/support/knowledgebase

cloud.google.com/bigquery/docs

docs.oracle.com/en/database/other-databases/nosql-database/index.html

splicemachine.com/how-it-works

www.tarantool.io/en/doc

Developer

Asthon Tate

Google

Oracle

Splice Machine

Initial release

1979

2010

2011

2014

2008

Current release

dBASE 2019, 2019

24.1, May 2024

3.1, March 2021

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

AGPL 3.0, commercial license available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

hosted

Linux
Solaris SPARC/x86

Linux
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

optional

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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 DML and DDL statements

yes

Full-featured ANSI SQL support

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

RESTful HTTP/JSON API

RESTful HTTP API

JDBC
Native Spark Datasource
ODBC

Open binary protocol

Supported programming languages

dBase proprietary IDE

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

yes

Java

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

none

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Multi-source replication
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

Since BigQuery is designed for querying data

configurable

ACID within a storage node (=shard)

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

off heap cache

yes

yes, full featured in-memory storage engine with persistence

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

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.