DBMS > BigchainDB vs. Greenplum vs. Linter vs. Quasardb vs. SQLite

System Properties Comparison BigchainDB vs. Greenplum vs. Linter vs. Quasardb vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

RDBMS for high security requirements

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.greenplum.org

doc.quasar.ai/master

www.sqlite.org/docs.html

Developer

Pivotal Software Inc.

relex.ru

quasardb

Dwayne Richard Hipp

Initial release

2016

2005

1990

2009

2000

Current release

7.0.0, September 2023

3.14.1, January 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C and C++

C++

Server operating systems

Linux

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

BSD
Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

integer and binary

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

since Version 4.2

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC

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

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
Java
Perl
Python
R

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

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

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

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

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

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

yes

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

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.