Pre-1.0 hoardDB is pre-1.0. Expect breaking changes.

Documentation

hoardDB is storage shaped by how you read. You pick the store that matches how you read, and every user, order or device keeps its own queues, maps and files. There are six stores (FIFO, LIFO, hash, btree, heap and blob). A bucket declares its fields, a field can be a store of any of the six types, and each document gets its own. The wire protocol is versioned binary over TCP+TLS.

You always choose the structure: user.Purchases is that user’s own queue, and hoardDB never picks one for you. A social network holds a person’s feed, friends and photos this way, and so can an order (its lines and events), a device (its readings) or a session (its history).

Ring mode (hoarddb -ring) is the engine these pages describe. A few pages were written before it and say at the top that they have not been rewritten yet.

Start with Installation, then Getting started. The sidebar lists every page.