5 releases
| new 0.2.1 | Nov 4, 2024 |
|---|---|
| 0.2.0 | Nov 3, 2024 |
| 0.1.2 | Oct 18, 2024 |
| 0.1.1 | Oct 14, 2024 |
| 0.1.0 | Oct 13, 2024 |
#300 in Debugging
605 downloads per month
55KB
1.5K
SLoC
Bulletin Board Server
Object storage for ArrayObject for debugging and data taking purposes.
BulletinBoard is a part of dbgbb project.
Highlights
- Hybrid backend of memory and file, selected based on the size of the object and the allocated memory.
- Key is a combination of a title and a tag. Each key contains revisions of
ArrayObject. - Simple access to data. For example, revision can be omitted. Then, the most recent revision is returned. The tag can also be omitted if no other tags are present.
- The commands
archiveanddumpmake data persistent. (Data does not persist by default.) - Docker image of the server is available.
Caution
- Clients do not check whether the operation is successful or not to improve performance. Check the log of the server for the errors.
- The data is not encrypted. Please do not send any confidential data over the network.
- This crate is under development and is subject to change in specification. (Compatibility across
BulletinBoardanddbgbbis ensured for the most minor version numbers.) - The included tests will access the server and potentially erase existing data.
Docker
The docker image is found here. (currently only available for arm64)
Example
Install and run the server with the specified listen address.
cargo install bulletin-board-server
export BB_LISTEN_ADDR = "0.0.0.0:7578"
bulletin-board-server
Environment Variables
| Variable | Default | Description |
|---|---|---|
| BB_LISTEN_ADDR | "127.0.0.1:7578" or "/tmp/bb.sock" | Listen address of the bulletin board server. When UNIX socket is used, the address should be the path to the uncreated socket. |
| BB_TMP_DIR | "./bb_tmp" | Directory for temporary data. |
| BB_ACV_DIR | "./bb_acv" | Directory for archives. |
| BB_TOT_MEM_LIMIT | "1GiB" | Total memory limit. If the memory exceeds the limit, all the bulletins are saved as files. The size of metadata is not included in the calculation. The actual memry consumption becomes higher than this. |
| BB_FILE_THRETHOLD | "1MiB" | Beyond this threthold, the bulletin is saved as a file. |
| BB_LOG_FILE | "./bulletin-board.log" | Location of the log file. |
Command line options
| Short | Long | Description |
|---|---|---|
| -d | --debug | Log to stdout. |
| -h | --help | Print help. |
| -V | --version | Print version. |
Crate Features
| Feature | Description |
|---|---|
unix |
Use the UNIX socket instead of TCP. Only for UNIX-like OS. |
Q&A
Why not persistent by default?
Since BulletinBoard was originally designed for debugging purposes, it is assumed that most of the data will be deleted at the end. Persistent options (archive and dump) have been added for a more extensive use such as data taking.
The advantages of not making it persistent by default are (i) holding data in memory makes read/write speeds faster, (ii) metadata of the archive becomes smaller and (iii) data can be more easily deleted before archiving.
Why not other object storages or databases?
Especially for debugging, storage may receive large amounts of small data and thus in-memory databases are ideal. However, it may also receive large data like a few hundred MiB, and such data should be stored in files. BulletinBoard uses a hybrid backend of memory and file to solve this problem.
Also, the BulletinBoard will not return a response if it is not needed. Thus, it can handle very frequent data flows.
Dependencies
~3–4MB
~72K SLoC