Apache HBase

HBase is an <a href="/facts/Open-source_software/HzTaB8E9">open-source</a> <a href="/facts/Non-relational_database/vvynRKfd">non-relational</a> <a href="/facts/Distributed_database/A6Q1s4Iy">distributed database</a> modeled after <a href="/facts/Google/GT9Sugza">Google's</a> <a href="/facts/Bigtable/xlXLKV0t">Bigtable</a> and written in <a href="/facts/Java_/9ScgFyAL">Java</a>. It is developed as part of <a href="/facts/Apache_Software_Foundation/Xl9Tt9lE">Apache Software Foundation</a>'s <a href="/facts/Hadoop/oUS1G2R7">Apache Hadoop</a> project and runs on top of <a href="/facts/Hadoop_Distributed_File_System/oUS1G2R7">HDFS (Hadoop Distributed File System)</a> or <a href="/facts/Alluxio/jpUDTLlD">Alluxio</a>, providing Bigtable-like capabilities for Hadoop. That is, it provides a <a href="/facts/Fault-tolerant/rasrYlJk">fault-tolerant</a> way of storing large quantities of <a href="/facts/Sparse_file/Q17UJTL8">sparse</a> data (small amounts of information caught within a large collection of empty or unimportant data, such as finding the 50 largest items in a group of 2 billion records, or finding the non-zero items representing less than 0.1% of a huge collection).
HBase features compression, in-memory operation, and <a href="/facts/Bloom_filter/Gq2WVE37">Bloom filters</a> on a per-column basis as outlined in the original Bigtable paper. Tables in HBase can serve as the input and output for <a href="/facts/Mapreduce/KbfxJ5vV">MapReduce</a> jobs run in Hadoop, and may be accessed through the Java API but also through <a href="/facts/REST/Q58zfr5h">REST</a>, <a href="/facts/Avro_(serialization_system)/eTn7FdRH">Avro</a> or <a href="/facts/Thrift_(protocol)/DWlecvw3">Thrift</a> gateway APIs. HBase is a <a href="/facts/Wide-column_store/qL6MGfhr">wide-column store</a> and has been widely adopted because of its lineage with Hadoop and HDFS. HBase runs on top of HDFS and is well-suited for fast read and write operations on large datasets with high throughput and low input/output latency.
HBase is not a direct replacement for a classic <a href="/facts/SQL/UjQLJcYm">SQL</a> <a href="/facts/Database/VYcpkevb">database</a>, however <a href="/facts/Apache_Phoenix/u4ILmg15">Apache Phoenix</a> project provides a SQL layer for HBase as well as <a href="/facts/JDBC/uUVYg2sB">JDBC</a> driver that can be integrated with various <a href="/facts/Analytics/JWD5D9cM">analytics</a> and <a href="/facts/Business_intelligence/ftThn7Wf">business intelligence</a> applications. The <a href="/facts/Apache_Trafodion/oakXeUlP">Apache Trafodion</a> project provides a SQL query engine with <a href="/facts/ODBC/2dV2Fm5j">ODBC</a> and <a href="/facts/JDBC/uUVYg2sB">JDBC</a> drivers and <a href="/facts/ACID/XdHkYzHN">distributed ACID transaction protection</a> across multiple statements, tables and rows that use HBase as a storage engine.
HBase is now serving several data-driven websites but <a href="/facts/Facebook/0IhXFR6u">Facebook</a>'s Messaging Platform migrated from HBase to <a href="/facts/MyRocks/P2WRvELg">MyRocks</a> in 2018. Unlike relational and traditional databases, HBase does not support SQL scripting; instead the equivalent is written in Java, employing similarity with a MapReduce application.
In the parlance of Eric Brewer's <a href="/facts/CAP_Theorem/qnxvcbLp">CAP Theorem</a>, HBase is a CP type system.

Apache HBase open-in-new

Apache HBase