DBMS > BigchainDB vs. dBASE vs. Graph Engine vs. SiteWhere vs. SQLite

System Properties Comparison BigchainDB vs. dBASE vs. Graph Engine vs. SiteWhere vs. SQLite

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Relational DBMS

Graph DBMS
Key-value store

Time Series DBMS

Relational DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.bigchaindb.com

www.dbase.com

www.graphengine.io

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

www.graphengine.io/docs/manual

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

Asthon Tate

Microsoft

SiteWhere

Dwayne Richard Hipp

Initial release

2016

1979

2010

2000

Current release

dBASE 2019, 2019

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

MIT License

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

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

Python

.NET and C

Java

Server operating systems

Linux

DOS

dBase Classic
Windows

dBase Pro

.NET

Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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-92 is not fully supported

APIs and other access methods

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

RESTful HTTP API

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

dBase proprietary IDE

C#
C++
F#
Visual Basic

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

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

yes

Access rights for users and roles

Users with fine-grained authorization concept

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.