DBMS > Apache Phoenix vs. BigObject vs. Couchbase

System Properties Comparison Apache Phoenix vs. BigObject vs. Couchbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Analytic DBMS for real-time computations and queries

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store

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	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Website

phoenix.apache.org

bigobject.io

www.couchbase.com

Technical documentation

phoenix.apache.org

docs.bigobject.io

docs.couchbase.com

Developer

Apache Software Foundation

BigObject, Inc.

Couchbase, Inc.

Initial release

2014

2015

2011

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

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

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free community edition available

Open Source

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

Cloud-based only

Only available as a cloud service

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

Linux
Unix
Windows

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
OS X
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

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

APIs and other access methods

JDBC

fluentd
ODBC
RESTful HTTP API

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

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

Lua

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

Triggers

yes

via the TAP protocol

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Multi-source replication

including cross data center replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

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.