As a developer, you would have a persistence at the (very) backend and create some efficient persistent mechanism for your data model (such as Schema, tables, relationship between tables, or NoSql, etc).
I learned that Dfinity introduced what they call Orthogonal Persistence (fancy name btw).
I wonder how can i understand this mechanism? I heard that the canister brings along your app as if every page contained the data itself. But is it a efficient model to store data like this, especially to scale up your end users (clients)? And can you manage the data or the protocol ‘takes care’ of the data model? How can we deploy a statistical model onto this kind of persistence?
Any more technical explanation of how this Orthogonal Persistence actually works as opposed to traditional way of persisting data?
Maybe too many question