DBMS > BigchainDB vs. Databricks vs. Linter vs. mSQL vs. SQLite

System Properties Comparison BigchainDB vs. Databricks vs. Linter vs. mSQL vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

RDBMS for high security requirements

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Document store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.bigchaindb.com

www.databricks.com

linter.ru

hughestech.com.au/products/msql

www.sqlite.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.databricks.com

www.sqlite.org/docs.html

Developer

Databricks

relex.ru

Hughes Technologies

Dwayne Richard Hipp

Initial release

2016

2013

1990

1994

2000

Current release

4.4, October 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

free licenses can be provided

Open Source

Public Domain

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

Python

C and C++

Server operating systems

Linux

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

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

server-less

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

with Databricks SQL

yes

A subset of ANSI SQL is implemented

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

yes

SQL-92 is not fully supported

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Python
R
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C++
Delphi
Java
Perl
PHP
Tcl

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

user defined functions and aggregates

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

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

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

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.