DBMS > Badger vs. dBASE vs. Google BigQuery vs. Splice Machine vs. Trafodion

System Properties Comparison Badger vs. dBASE vs. Google BigQuery vs. Splice Machine vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Key-value store

Relational DBMS

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

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

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

Website

github.com/dgraph-io/badger

www.dbase.com

cloud.google.com/bigquery

splicemachine.com

trafodion.apache.org

Technical documentation

godoc.org/github.com/dgraph-io/badger

www.dbase.com/support/knowledgebase

cloud.google.com/bigquery/docs

splicemachine.com/how-it-works

trafodion.apache.org/documentation.html

Developer

DGraph Labs

Asthon Tate

Google

Splice Machine

Apache Software Foundation, originally developed by HP

Initial release

2017

1979

2010

2014

Current release

dBASE 2019, 2019

3.1, March 2021

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

AGPL 3.0, commercial license available

Open Source

Apache 2.0

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

DOS

dBase Classic
Windows

dBase Pro

hosted

Linux
OS X
Solaris
Windows

Linux

Data scheme

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

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

RESTful HTTP/JSON API

JDBC
Native Spark Datasource
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

dBase proprietary IDE

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

yes

Java

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

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

fine grained access rights 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.