Awesome answer. Thank you @ericnormand !
Yeah, I know, this problem it’s somewhat at the “fringe” of re-frame (or even orthogonal), yet I suspect it’s becoming quite common with modern web apps nowadays, well beyond the canonical old “chat” scenario (I’m looking at trello-like apps where card state is propagated in realtime).
Eh eh, a good example about “how” to sync state seems like it could be a great followup to the excellent existing lesson about choosing “where” to store it
Frankly, I was already digging into HTTPKit/Sente as I saw quite a few people referring to it.
It might be my first attempt as it’s somewhat more familiar and builds upon stacks I already use.
Pedestal seems like a great contender, but I’ll have to investigate further.
I honestly had somewhat ruled out Aleph simply on the basis that the resources I found where a bit old.
Stupid, I know. If it works, it works.
Thanks indeed for the insights about how we may approach the problem in Re-frame.
One thing I truly love about re-frame is that the separation of concerns allow us to delay (or even revert) these decisions about what to use relatively easily.
Heck, I might keep working on the in-memory DB and/or plain xhrio calls for the time being