Hi 🙂 that post on http://juxt.pro is definitely out of date now (sorry!) but it did get re-posted and freshly updated with the new API here on the http://opencrux.com site though: https://opencrux.com/blog/crux-confluent-cloud.html Out of interest, how did you stumble on to that http://juxt.pro version?

I'll make a note to update that old post, or at least place a clear note at the top of the page with a pointer to the up-to-date resource :thumbsup:

Thanks for the link to the updated tutorial! I came across the old one via reddit (https://www.reddit.com/r/Clojure/comments/cmqhdd/crux_with_confluent_cloud_kafka_in_5_minutes/). Basically, I'm looking for the easiest way to get started with Crux for a hobby project that needs persistence. I thought that Confluent Cloud would be the way to go, but now I see that I'd need RocksDB to persist the indexes. I'm thinking that I might be better off just using RocksDB for all 3 of transaction log, document store, and index store. RocksDB just stores to disk, right, sort of like SQLite?

yup, rocksdb is a kvstore on your local disk. If local disk persistence is good enough then using it for everything is the way to go

awesome, thanks for the tips 👍

@UA9399DFZ We're in the process of reorganizing documentation a bit. Out of curiosity, would an introductory tutorial walking you through the simplest persistent setup (just as you mentioned, 3 Rocks instances for each of the 3 stores) be something you would have liked to have seen when you were navigating the docs and blog posts?

Yes, that would be great! I really like that you've made it so easy to get started with the in-memory db, so there's no friction to start on the "https://juxt.pro/blog/crux-tutorial-setup" tutorial. It would be great to have an obvious next step after that for when persistence is needed.

@UA9399DFZ Thanks... I've suspected as much for a while, but it's great to hear it directly. 🙂