DBMS > BigchainDB vs. Google Cloud Bigtable vs. PostGIS vs. SQLite vs. Valentina Server

System Properties Comparison BigchainDB vs. Google Cloud Bigtable vs. PostGIS vs. SQLite vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Spatial extension of PostgreSQL

Widely used embeddable, in-process RDBMS

Object-relational database and reports server

Primary database model

Document store

Key-value store
Wide column store

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

www.bigchaindb.com

cloud.google.com/bigtable

postgis.net

www.sqlite.org

www.valentina-db.net

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/bigtable/docs

postgis.net/documentation

www.sqlite.org/docs.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Google

Dwayne Richard Hipp

Paradigma Software

Initial release

2016

2015

2005

2000

1999

Current release

3.4.2, February 2024

3.45.3 (15 April 2024), April 2024

5.7.5

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

GPL v2.0

Open Source

Public Domain

commercial

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

Server operating systems

Linux

hosted

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

APIs and other access methods

CLI Client
RESTful HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

based on PostgreSQL

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

based on PostgreSQL

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.