DBMS > Google Cloud Bigtable vs. IBM Cloudant vs. Sadas Engine vs. XTDB

System Properties Comparison Google Cloud Bigtable vs. IBM Cloudant vs. Sadas Engine vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering based on Apache CouchDB

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Primary database model

Key-value store
Wide column store

Document store

Relational DBMS

Document store

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

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Score	0.09
Rank	#351	Overall
	#47	Document stores

Website

cloud.google.com/bigtable

www.ibm.com/products/cloudant

www.sadasengine.com

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

Technical documentation

cloud.google.com/bigtable/docs

cloud.ibm.com/docs/Cloudant

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

www.xtdb.com/docs

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

SADAS s.r.l.

Juxt Ltd.

Initial release

2015

2010

2006

2019

Current release

8.0

1.19, September 2021

License

Commercial or Open Source

commercial

free trial version available

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

Erlang

C++

Clojure

Server operating systems

hosted

AIX
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

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

SQL

Support of SQL

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

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

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol

HTTP REST
JDBC

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication
Source-replica replication

none

yes, each node contains all data

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)

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

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

managed by 'Learn by Usage'

User concepts

Access control

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

Access rights for users can be defined per database

Access rights for users, groups and roles 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.

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

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

What is Google Bigtable? | Definition from TechTarget
1 March 2022, TechTarget

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, ibm.com

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, ibm.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

Share this page