Hibari DB
== Application Developer’s Guide ==
Table of Contents
Introduction
Why NOSQL?
Why Hibari?
Engineered in Erlang
Chain Replication for High Availability and Strong Consistency
Easy, Affordable Scalability
High Performance, Especially for Reads and Large Values
Simple But Powerful Client API
Production-Proven
Hibari Benefits for Developers, System Administrators, and Businesses
Getting Started
System Requirements
Required Third-Party Software
Downloading Hibari
Installing a Single-Node Hibari System
Starting and Stopping Hibari on a Single Node
Installing a Multi-Node Hibari Cluster
Creating New Tables
The Hibari Data Model
Hibari Client API Overview
Supported Operations
Check and Swap (CAS)
Micro-Transaction
Client API: Native Erlang
Data Insertion
Data Retrieval
Data Deletion
Compound Operations
Fold Operations
brick_simple:add/6
brick_simple:replace/6
brick_simple:set/6
brick_simple:rename/6
brick_simple:get/4
brick_simple:get_many/5
brick_simple:delete/4
brick_simple:do/4
brick_simple:fold_table/7
brick_simple:fold_key_prefix/9
Client API: UBF
The Hibari Server’s Implementation of the UBF Protocol Stack
UBF representation of strings vs. binaries
Steps for Using a UBF-based Protocol in Any Language
The Hibari UBF Protocol Contract
Using the UBF Client Library for Erlang
Using the UBF Client Library for Java
Using the EBF Client Library for Python
Client API: Thrift
The Hibari Thrift API
Mapping UBF Contract Types to Thrift Types
Mapping UBF Contract to Thrift Service
Examples of using a Thrift client
Mapping TBF Contract Responses From Thrift Client
Building Hibari from Source
Required Third Party Software
Downloading Hibari
Building the Hibari Release Package
Building Hibari’s Documentation
Building and Installing Erlang/OTP
Contributing to Hibari
GitHub, Git, and Repo
Code, Branch, and Version Management
Documentation
Submitting Patches
== System Admin Guide ==
DRAFT - IN PROGRESS
Table of Contents
Introduction
The Problem
Key-Value Store
Hibari’s Origins
Summary of Hibari’s Main Features
The “ACID vs. BASE” Spectrum and Hibari
The CAP Theorem and Hibari
Hibari’s Main Features in Broad Detail
Building A Hibari Database
Hibari Architecture
Bricks, Physical and Logical
The Admin Server Application
Hibari System Information: Configuration Files, Etc.
The Life of a (Logical) Brick
Dynamic Cluster Reconfiguration
The Partition Detector Application
Backup and Disaster Recovery
Hibari Application Logging
Hardware and Software Considerations
Administering Hibari Through the API
brick_admin:add_table(stack, ChainList, Opts).
.Create a new stack
.Push an item onto a stack
.Pop an item off a stack
Item.
.Data types for brick_admin:change_chain_length()
.Data types for brick_admin:start_migration()
(hibari1@bb3)63> OldFloatMap = brick_hash:chash_extract_new_float_map(OldGH).
== Contributor’s Guide ==
DRAFT - IN PROGRESS
Table of Contents
Copyright
Hibari DB
Docs
»
Hibari Contributor’s Guide (Hibari v0.1.11)
Edit on GitHub
Hibari Contributor’s Guide (Hibari v0.1.11)
¶
DRAFT - IN PROGRESS
¶
Date:
2015/03/22
Revision:
0.5.4
Copyright (C) 2005-2015 Hibari developers. All rights reserved.
Table of Contents
¶
Read the Docs
v: latest
Versions
latest
Downloads
htmlzip
epub
On Read the Docs
Project Home
Builds
Free document hosting provided by
Read the Docs
.