DBMS > Alibaba Cloud Table Store vs. Apache Druid vs. Couchbase vs. Google Cloud Firestore vs. Postgres-XL

System Properties Comparison Alibaba Cloud Table Store vs. Apache Druid vs. Couchbase vs. Google Cloud Firestore vs. Postgres-XL

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Wide column store

Relational DBMS
Time Series DBMS

Document store

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

Document store
Spatial DBMS

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

Score	0.25
Rank	#294	Overall
	#12	Wide column stores

Score	2.85
Rank	#96	Overall
	#50	Relational DBMS
	#6	Time Series DBMS

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	0.43
Rank	#260	Overall
	#119	Relational DBMS

Website

www.alibabacloud.com/product/table-store

druid.apache.org

www.couchbase.com

firebase.google.com/products/firestore

www.postgres-xl.org

Technical documentation

www.alibabacloud.com/help/en/tablestore

druid.apache.org/docs/latest/design

docs.couchbase.com

firebase.google.com/docs/firestore

www.postgres-xl.org/documentation

Developer

Alibaba

Apache Software Foundation and contributors

Couchbase, Inc.

Google

Initial release

2016

2012

2011

2017

2014

since 2012, originally named StormDB

Current release

30.0.0, June 2024

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

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

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

commercial

Open Source

Mozilla public 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

Java

C, C++, Go and Erlang

Server operating systems

hosted

Linux
OS X
Unix

Linux
OS X
Windows

hosted

Linux
macOS

Data scheme

schema-free

yes

schema-less columns are supported

schema-free

yes

Typing

predefined data types such as float or date

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

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

yes

distributed, parallel query execution

APIs and other access methods

HTTP API

JDBC
RESTful HTTP/JSON API

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

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Java
Python

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

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

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes

via the TAP protocol

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

manual/auto, time-based

Automatic Sharding

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes, via HDFS, S3 or other storage engines

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

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

yes

ACID

MVCC

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

Ephemeral buckets

User concepts

Access control

Access rights based on subaccounts and tokens

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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. Security Rules for 3rd party authentication using Firebase Auth.

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.