tl;dr: Do I need a full blown cloud setup when I want to host a simple app with xtdb on azure? Can I go simpler? Has anyone had experience with that? Details (in code block for less visual noise)
I am currently evaluating how to deploy xtdb for a small, simple web app that is used internally. There will be about three users, most of the time not even in parallel and the mvp is really just a few crud operations and a bit of data analysis. It's going to become more complex obviously, and I especially hope that incoming audit requirements will be a bit less painful to fulfill with xtdb.
I would guess that just putting my webserver + xtdb with filesystem storage in a container app on azure is a bit too simple, but I would prefer not having to do a devops deepdive as indicated in the docs. What are my options?
I too wish for straightforward documentation about how to do local disk storage / indexing with xtdb2 for local dev and even small apps that don't really need all the fancy
Follow up question: Could I migrate from filesystem log to kafka if necessary?
I wrote up some findings here a while ago: https://clojurians.slack.com/archives/C013Y4VG20J/p1758282350537819?thread_ts=1758282350.537819&cid=C013Y4VG20J more recently I've been finally migrating a bunch of data into xtdb2 and I have unfortunately run into some weirdness (an ingestion stopped error, maybe a corrupted transaction?) when using the file system log that I didn't get with red panda. I want to investigate that some more because it would be nice to not have the extra moving part of redpanda. however redpanda is fairly lightweight so there's that, and you can run an instance of it alongside your app process if you want.
Cool, thanks! That'll probably save me a huge amount of time!