apache/phoenix

Health v2 · maintenance only

Adoption not part of the score

1060 stars · 1009 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Apache Phoenix is a SQL layer over Apache HBase delivered as a client-embedded JDBC driver, compiling standard SQL queries into low-latency HBase scans. It provides OLTP and operational analytics on Hadoop with ACID transactions, secondary indexing, BSON document support, and change data capture.

Use cases

• query hbase data with standard sql and jdbc
• run low-latency oltp workloads on hadoop
• add secondary indexes to hbase tables for fast lookups
• stream row-level change events from a table with cdc
• store and query schemaless bson documents alongside relational columns
• build multi-tenant saas applications with tenant isolation
• run etl pipelines integrating hbase with spark and hive
• point dynamodb sdk applications at a self-hosted cluster

When to choose

• you already run hbase and want sql access with millisecond latency
• you need ACID transactions and secondary indexes over HBase data
• you want operational analytics integrated with the Hadoop ecosystem (Spark, Hive, Pig)
• you need DynamoDB-compatible APIs without AWS lock-in

When to avoid

• you are starting a greenfield project with no existing HBase investment
• you need a general-purpose standalone SQL database like PostgreSQL
• your workload is pure batch analytics better served by a data warehouse
• you cannot operate an HBase cluster and its operational complexity

Facets

library · maturity active

database database-driver search-engine streaming databases big-data analytics jvm cloud self-hosted sql jdbc hbase hadoop nosql oltp secondary-indexes change-data-capture bson spark-integration data-engineering linux

Member repositories

For agents

markdown · JSON · MCP: product_card(name="apache/phoenix")