DBMS > Alibaba Cloud Table Store vs. Couchbase vs. Google Cloud Bigtable vs. Graphite vs. Ingres

System Properties Comparison Alibaba Cloud Table Store vs. Couchbase vs. Google Cloud Bigtable vs. Graphite vs. Ingres

Editorial information provided by DB-Engines

Name

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Well established RDBMS

Primary database model

Wide column store

Document store

Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

Score	16.59
Rank	#36	Overall
	#5	Document stores

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

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Website

www.alibabacloud.com/product/table-store

www.couchbase.com

cloud.google.com/bigtable

github.com/graphite-project/graphite-web

www.actian.com/databases/ingres

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.couchbase.com

cloud.google.com/bigtable/docs

graphite.readthedocs.io

docs.actian.com/ingres

Developer

Alibaba

Couchbase, Inc.

Google

Chris Davis

Actian Corporation

Initial release

2016

2011

2015

2006

1974

originally developed at University Berkely in early 1970s

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

11.2, May 2022

License

Commercial or Open Source

commercial

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

Open Source

Apache 2.0

commercial

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

C, C++, Go and Erlang

Python

Server operating systems

hosted

Linux
OS X
Windows

hosted

Linux
Unix

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

APIs and other access methods

HTTP API

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

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

HTTP API
Sockets

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

Supported programming languages

Java
Python

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Automatic Sharding

Sharding

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication

including cross data center replication
Source-replica replication

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

none

Ingres Replicator

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

MVCC

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

Ephemeral buckets

User concepts

Access control

Access rights based on subaccounts and tokens

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base 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

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.