Shared data types are currently maintained as last-snapshot plus operations-since (oplog). We need to allow for collapsing the oplog into a new snapshot.
Optimal collapse schedule may be datatype-specific
This is separate to the Journal, but may benefit from shared configuration
Note that an active shared data type (by LRU) is maintained in memory so does not suffer compounding performance issues because of this, but it will affect hydration time for newly active data
Shared data types are currently maintained as last-snapshot plus operations-since (oplog). We need to allow for collapsing the oplog into a new snapshot.
See also m-ld/m-ld-spec#24