DBMS > BigchainDB vs. Google Cloud Datastore vs. Infobright vs. XTDB

System Properties Comparison BigchainDB vs. Google Cloud Datastore vs. Infobright vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Primary database model

Document store

Relational DBMS

Document store

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

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

www.bigchaindb.com

cloud.google.com/datastore

ignitetech.com/softwarelibrary/infobrightdb

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

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/datastore/docs

www.xtdb.com/docs

Developer

Google

Ignite Technologies Inc.; formerly InfoBright Inc.

Juxt Ltd.

Initial release

2016

2008

2005

2019

Current release

1.19, September 2021

License

Commercial or Open Source

Open Source

AGPL v3

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

MIT License

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

Clojure

Server operating systems

Linux

hosted

Linux
Windows

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

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

CLI Client
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

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

Multi-source replication using Paxos

Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

yes

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Using BigchainDB: A Database with Blockchain Characteristics
20 January 2022, Open Source For You

Top 10 startups in Digital Twin in Germany
11 July 2024, Tracxn

7 blockchain firms join Bosch led GAIA-X consortium for vehicle identity
13 September 2022, Ledger Insights

BigchainDB: A Popular and Powerful Database for Blockchain
9 September 2019, Open Source For You

How to use blockchain to build a database solution
2 March 2017, ZDNet

provided by Google News

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
13 September 2024, TechRadar

Google App Engine
26 April 2024, TechTarget

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

Share this page