DBMS > Apache Phoenix vs. Google BigQuery vs. Hive vs. Linter vs. OrigoDB

System Properties Comparison Apache Phoenix vs. Google BigQuery vs. Hive vs. Linter vs. OrigoDB

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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

RDBMS for high security requirements

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Spatial DBMS

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	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

phoenix.apache.org

cloud.google.com/bigquery

hive.apache.org

linter.ru

origodb.com

Technical documentation

phoenix.apache.org

cloud.google.com/bigquery/docs

cwiki.apache.org/confluence/display/Hive/Home

origodb.com/docs

Developer

Apache Software Foundation

Google

Apache Software Foundation

initially developed by Facebook

relex.ru

Robert Friberg et al

Initial release

2014

2010

2012

1990

2009

under the name LiveDB

Current release

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

3.1.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2

commercial

Open Source

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

Server operating systems

Linux
Unix
Windows

hosted

All OS with a Java VM

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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 be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC

RESTful HTTP/JSON API

JDBC
ODBC
Thrift

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

.NET Client API
HTTP API
LINQ

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
PHP
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

.Net

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions and integration of map-reduce

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

fine grained access rights according to SQL-standard

Role based authorization

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.