DBMS > Badger vs. dBASE vs. Spark SQL vs. SQLite vs. XTDB

System Properties Comparison Badger vs. dBASE vs. Spark SQL vs. SQLite vs. XTDB

Editorial information provided by DB-Engines

Name

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.

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store

Relational DBMS

Document store

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	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

github.com/dgraph-io/badger

www.dbase.com

spark.apache.org/sql

www.sqlite.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

www.dbase.com/support/knowledgebase

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

www.xtdb.com/docs

Developer

DGraph Labs

Asthon Tate

Apache Software Foundation

Dwayne Richard Hipp

Juxt Ltd.

Initial release

2017

1979

2014

2000

2019

Current release

dBASE 2019, 2019

3.5.0 ( 2.13), September 2023

3.46.0 (23 May 2024), May 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

MIT License

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Clojure

Server operating systems

BSD
Linux
OS X
Solaris
Windows

DOS

dBase Classic
Windows

dBase Pro

Linux
OS X
Windows

server-less

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes, extensible-data-notation format

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

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP REST
JDBC

Supported programming languages

dBase proprietary IDE

Java
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Clojure
Java

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.