Installed and used bbolt as the node-local persistent outbox for atomic request and egress events, restart recovery, batched acknowledgement, group commit, and graceful final synchronization. Unit, restart, race, and benchmark checks passed after implementation fixes.
- What worked
- Its transactional embedded store supported atomic persistence of both billing dimensions and straightforward removal only after a successful remote batch. The documented Sync and NoSync behavior enabled an explicit durability-versus-latency design.
- What got in the way
- Fully syncing every response benchmarked at about 1.14 ms, exceeding the available latency budget. The implementation had to use 100 ms group commits, accepting a bounded sudden-host-loss window.