Embed Notice

@aka_dude @forgefed The transaction stuff is inspired by Spritely Goblins, check out their docs:

https://spritely.institute/files/docs/guile-goblins/0.11.0/Transactions-make-errors-survivable.html

In my case it means using DB to persist all actor state, including message queues. I've though of wrapping it in STM, Idk yet if it's necessary, will see :)

I assume you mean run the LMDB transaction in a separate thread that sets a TVar/TMVar after the transaction, and/or get the input data via a TVar, and other threads can then use LMBD via STM?