biff

A web framework + self-hosted deployment solution for Clojure. Repo: https://github.com/jacobobryant/biff. Docs: https://biff.findka.com
2020-07-21T14:45:27.005700Z

I have been following the progress with Materialize but I am unsure of the benefit. Is it speed, scaling or both? My application will need to maintain an updated log of transactions — close to real time but speed isn’t that critical — Am I correct that I could just use postgres and hosted postgres, for example, on Digital Ocean as an alternative for materialize-- Also the last post mentioned overhead for development - but can’t I just develop locally with Rocksdb and text file storage then when I get set switch out the backend

2020-07-21T20:55:18.027900Z

Yes, postgres + rocksdb will most likely be fine. In most cases materialize probably won't be needed at all. The benefit of materialize is that it can speed up queries. If you have some long-running query that you normally would run in a cron job and store the results, materialize will instead let you run the query quickly whenever you want and get an up-to-date response. The most common example is probably business intelligence kinds of queries, like how many active users are there currently etc. With findka specifically there are more uses since it's a recommender system and the whole point of it is to aggregate information from all the data. In most cases, running expensive queries in batch is probably fine. I'm getting by alright doing that with Findka. Materialize would make things a little more convenient in my case though, and it'll become more useful as my app accumulates features + data. And, to be honest, half the reason I'm working on the materialize integration is just out of curiosity. I'm interested to see if I can find additional ways to simplify common web dev tasks once I have it in place. (also, some clarification--even when materialize is integrated, it won't replace postgres or rocksdb. It'll be an additional component that receives data from crux)