The typical schema mismatch of 'persisted data' (RDBMS, KV, ...) vs 'app in memory data' (lists, dicts, structs, ...) vs 'views' (tables, lists, ...) requires all this data shuffling. Would be nice to have one model where persistence and computation layers can be easily added.https://twitter.com/jonathoda/status/1245816174568525824 …
-
-
I have now
Can't say I got it all, but in general I agree with the ideas that orthogonal persistence should exist at the 'higher' levels, allow diverse and evolvable lower level implementations, and enable flexible consistency properties. -
I don't think of 'orthogonal persistence' as a general computing problem because it arose from a very specific context: fast volatile RAM + slow disks. We designed the computing and persistence model in this context, when in fact there is nothing fundamental about this divide.
End of conversation
New conversation -
-
-
Yes but I didn’t understand it
-
Mea culpa, then. Next time we meet in person (or online?) let's discuss it and see how I may improve the explanation. The story format has its advantages and limitations.
- 1 more reply
New conversation -
-
-
Ann changed my life
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!