[…] implementing Auto Save in the RDBMS system could be a problem because of multiple reasons:
- The schema and overall logic changes to save versioned data in the RDBMS system will be non-trivial
- There might be validation checks that fail because users kept didn’t fill out some fields at that point.
- Making periodic (30 second) transactional updates to any live system is not good for overall performance.
A work around would be saving your Object Model to RavenDB directly and if user visits the document after a time out, load both Transactional Data and Object data, compare the timestamp and use the freshest set of data.
By far the best document database usecase I have read about in quite a while.
Original title and link: Implementing Auto Saves Using RavenDB: NoSQL Tutorials ( ©myNoSQL)