[…] 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)
RavenDB still has a weakness that prevents it from becoming the instant choice of all green-field (a project starting fresh) ASP.NET MVC web projects. Most reporting solutions today work best off RDBMS systems and NoSQL databases are just getting their feet wet with respect to Reporting system connectivity.
So if you are building a system that doesn’t require traditional reporting systems to hook in and retrieve data, RavenDB is the perfect choice. More often that not, that’s not the case (specially Line of Business applications) and hence we tend to fallback on SQL Server/MySQL/Oracle etc.
Leaving aside the (very) short bullet point definition of RavenDB, the conclusion sounds confusing. It makes me wonder if the majority of ASP.NET projects are mostly about reporting.
Original title and link: Introducing RavenDB for ASP.NET Developers: NoSQL Tutorials ( ©myNoSQL)