DBMS > BoltDB vs. Google Cloud Datastore vs. Heroic vs. RocksDB vs. TiDB

System Properties Comparison BoltDB vs. Google Cloud Datastore vs. Heroic vs. RocksDB vs. TiDB

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Secondary database models

Document store

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.66
Rank	#70	Overall
	#38	Relational DBMS

Website

github.com/boltdb/bolt

cloud.google.com/datastore

github.com/spotify/heroic

rocksdb.org

pingcap.com

Technical documentation

cloud.google.com/datastore/docs

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

docs.pingcap.com/tidb/stable

Developer

Google

Spotify

Facebook, Inc.

PingCAP, Inc.

Initial release

2013

2008

2014

2013

2016

Current release

8.11.4, April 2024

8.0.0, March 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache 2.0

Open Source

BSD

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

Java

C++

Go, Rust

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

schema-free

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

APIs and other access methods

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

GORM
JDBC
ODBC
Proprietary protocol
SQLAlchemy

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

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

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

horizontal partitioning (by key range)

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

yes

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

yes

with TiSpark Connector

Consistency concepts

Methods to ensure consistency in a distributed system

none

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.

Eventual Consistency
Immediate Consistency

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

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

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.