DBMS > Apache Phoenix vs. Google BigQuery vs. Google Cloud Bigtable vs. Manticore Search

System Properties Comparison Apache Phoenix vs. Google BigQuery vs. Google Cloud Bigtable vs. Manticore Search

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

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.

Multi-storage database for search, including full-text search.

Primary database model

Relational DBMS

Key-value store
Wide column store

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Website

phoenix.apache.org

cloud.google.com/bigquery

cloud.google.com/bigtable

manticoresearch.com

Technical documentation

phoenix.apache.org

cloud.google.com/bigquery/docs

cloud.google.com/bigtable/docs

manual.manticoresearch.com

Developer

Apache Software Foundation

Google

Manticore Software

Initial release

2014

2010

2015

2017

Current release

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

6.0, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2

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++

Server operating systems

Linux
Unix
Windows

hosted

FreeBSD
Linux
macOS
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

Fixed schema

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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 index from XML

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

JDBC

RESTful HTTP/JSON API

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

Synchronous replication based on Galera library

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

Immediate Consistency

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

Foreign keys

Referential integrity

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

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

In-memory capabilities

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

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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)

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.