Fork me on GitHub
Reshef Mann10:10:13

Hi. how are reified transactions ( are performed on Crux? Could find a mention in the docs. Thanks


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.: What kind of things are you hoping to do with reified transactions?

Reshef Mann11:10:48

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

🙏 6
Christopher Thonfeld-Guckes13:10:23

If I use kafka for documents and the transaction-log, do I still need persistence for the index store? Specifically I'm asking, can I deploy my application to heroku and use confluent's service to fully use crux?

Christopher Thonfeld-Guckes13:10:13

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

✔️ 3

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

Christopher Thonfeld-Guckes14:10:19

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

notbad 9