DBMS > CockroachDB vs. Google BigQuery vs. Google Cloud Bigtable vs. OrigoDB

System Properties Comparison CockroachDB vs. Google BigQuery vs. Google Cloud Bigtable vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

Large scale data warehouse service with append-only tables

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

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Key-value store
Wide column store

Document store
Object oriented DBMS

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

www.cockroachlabs.com

cloud.google.com/bigquery

cloud.google.com/bigtable

origodb.com

Technical documentation

www.cockroachlabs.com/docs

cloud.google.com/bigquery/docs

cloud.google.com/bigtable/docs

origodb.com/docs

Developer

Cockroach Labs

Google

Robert Friberg et al

Initial release

2015

2010

2015

2009

under the name LiveDB

Current release

24.1.0, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

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

Server operating systems

Linux
macOS
Windows

hosted

Linux
Windows

Data scheme

dynamic schema

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

APIs and other access methods

JDBC

RESTful HTTP/JSON API

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

.NET Client API
HTTP API
LINQ

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

In-memory capabilities

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

yes

User concepts

Access control

Role-based access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

Role based authorization

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.