Problem

Using BookKeeper as a low-latency distributed data storage

The primary purpose of BookKeeper is to be used as distributed transaction log, but for its internal design it can be used as a distributed storage of binary data.

The idea is to store binary objects (BLOBS) as entries inside ledgers. In this case there is no need for "tailing reads" or "fencing".

This way of working can be drafted with this every simple scenario:

• Writers create ledgers, writes BLOBS to them and store to an external database the ID of each BLOB a pair (ledgerid, entryid) as BLOB_ID
• Once a write as been acked by the configured quorum of bookies the BLOB can be considered to be stored in a durable storage
• Readers can use the BLOB_IDs to access data reading directly from any of the the bookies which contain a copy of the BLOB

Design

TBD

Actions

TBD