To keep track of changes and sync, realm platform stores the whole transaction history on the server, is that correct? I am wondering if this is somehow exposed to the API and could be used for a Undo/Redo history or snapshot feature rather than implementing this separately in the database by double-tracking the projects history.
any ideas on this ? Or examples how to simply implement snapshots/history maybe?
@chuck We do not expose the operation log to higher level APIs but we do have an Adapter API that would allow you to capture all of the changes and then push them into a queue like Kafka where you could later play it back