DBMS > BigchainDB vs. Google Cloud Datastore vs. Oracle vs. TiDB

System Properties Comparison BigchainDB vs. Google Cloud Datastore vs. Oracle vs. TiDB

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

Widely used RDBMS

TiDB is an open source distributed SQL database that supports Hybrid Transactional/Analytical Processing (HTAP) workloads. It is MySQL compatible and features horizontal scalability, strong consistency, and high availability.

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Document store

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	4.66
Rank	#70	Overall
	#38	Relational DBMS

Website

www.bigchaindb.com

cloud.google.com/datastore

www.oracle.com/database

pingcap.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/datastore/docs

docs.oracle.com/en/database

docs.pingcap.com/tidb/stable

Developer

Google

Oracle

PingCAP, Inc.

Initial release

2016

2008

1980

2016

Current release

23c, September 2023

8.0.0, March 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

restricted free version is available

Open Source

Apache 2.0

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.

TiDB Cloud: Fully-managed TiDB Service. Bring everything great about TiDB to the cloud.

Implementation language

Python

C and C++

Go, Rust

Server operating systems

Linux

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes, details here

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

SQL-like query language (GQL)

yes

with proprietary extensions

yes

APIs and other access methods

CLI Client
RESTful HTTP API

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

GORM
JDBC
ODBC
Proprietary protocol
SQLAlchemy

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

using Google App Engine

PL/SQL

also stored procedures in Java possible

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

horizontal partitioning (by key range)

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

can be realized in PL/SQL

yes

with TiSpark Connector

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

yes

full support since version 6.6

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Version 12c introduced the new option 'Oracle Database In-Memory'

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

Fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

TiDB is an advanced open-source, distributed SQL database for modern application...
» more

Competitive advantages

- HORIZONTAL SCALING : TiDB grants total transparency into your data workloads without...
» more

Typical application scenarios

TiDB is ideal for transactional applications that require extreme scalability and...
» more

Key customers

Block, Pinterest, Catalyst, Bolt, Flipkart, Capcom, Shopee (E-commerce), JD Cloud...
» more

Market metrics

34K+ GitHub stars 5K+ members in TiDB Community Slack 1K+ community contributors...
» more

Licensing and pricing models

TiDB Community : Free open source software (Apache 2.0) TiDB Self-Hosted : Enterprise...
» 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.