One database, two applications, second level caching and NHibernate

Question

What I need to know when setting up caching using NHibernate, in case I have two applications running on different servers, but only one database. Are there enough dependencies in the table to make sure that strange caching problems do not occur? If so, which poll should I look at?

Answer 1

Well, for nhibernate to check concurrency problems, you can add a field to your objects. This will cause nhibernate to throw a concurrency exception when trying to update an object that has been modified by someone else.

, nhibernate, NCache: http://www.alachisoft.com/ncache/nhibernate_index.html