Are there ideas in place for future releases to limit how fast the db grows with snapshots...

Such as having a master snapshot that isn't touched and then just have deltas written out for consecutive snapshots. If a new identity or application source is detected, it takes a new master snapshot and the old master snapshot is held for retention values for the customer to clean up as desired. Idea is that if an environment is fairly stagnant but they run collections often, you wouldn't have a lot of snapshots, just deltas.

Customer is concerned with how fast the snapshots grow the database and how much retention they can have for reporting, etc.

Granted, this is my limited knowledge of the architecture and scalability factors.

thanks,
Fred