Hello 🙂 Crux doesn't provide any transaction reification out-of-the-box, although you should be able to recreate exactly what you need in user space, potentially with help from transaction functions, e.g.: https://gist.github.com/refset/a00be06443bc03ccc84a2874af3cdb8a#file-txfns-clj-L1-L8 What kind of things are you hoping to do with reified transactions?

Thanks. Really helpful. I want to capture the user intent that caused the transaction a la cqrs.

NVM, the documentation states, that the indices will be rebuilt from the other two stores.

Yes, but beware that this might take some while. So better not depend on it for a lambda, e.g. 🙂

Ah, ok. Heroku restarts once every 24h, that should be fine for a hobby app...

^ all this is correct. I think as long as the per-dyno index size for the app stays healthily below the per-dyno memory limits then this setup should be fine for a hobby app 🙂 However, beware that the bandwidth costs may start racking up if restarts happen too often!

FYI I’ve got a german hoster with a nifty small cloud plan. Virtual host starts at 2.89€/month