DBMS > dBASE vs. Google BigQuery vs. mSQL vs. Splice Machine vs. Typesense

System Properties Comparison dBASE vs. Google BigQuery vs. mSQL vs. Splice Machine vs. Typesense

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Relational DBMS

Search engine

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	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	0.76
Rank	#219	Overall
	#14	Search engines

Website

www.dbase.com

cloud.google.com/bigquery

hughestech.com.au/products/msql

splicemachine.com

typesense.org

Technical documentation

www.dbase.com/support/knowledgebase

cloud.google.com/bigquery/docs

splicemachine.com/how-it-works

typesense.org/docs

Developer

Asthon Tate

Google

Hughes Technologies

Splice Machine

Initial release

1979

2010

1994

2014

2015

Current release

dBASE 2019, 2019

4.4, October 2021

3.1, March 2021

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

AGPL 3.0, commercial license available

Open Source

GPL V3

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++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

pre-defined schema optional

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

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

RESTful HTTP/JSON API

JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

RESTful HTTP API

Supported programming languages

dBase proprietary IDE

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

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

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication using RAFT

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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 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 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.