On Feb 9, 8:49 am, Henning <[email protected]> wrote: > Hi, > > I have a web-based application, which is served on a couple of load- > balanced web-servers. To boost performance I would like to enable > caching. But what would happen if data is being written to the DB on > one of the web-servers, how do the other server know to drop their > cached instances? What would be the best practice?
Please note that memcached is NOT a true distributed cache. It's a dumb cache which uses distributed hashing with no redundancy. If your memcache fails, so does your application unless you code around it. Memcache is a good piece of kit, but it requires some thinking rather than blind application. http://code.google.com/p/memcached/wiki/FAQ#How_is_memcached_redundant? We've been using Velocity CTP2 and NH2 together successfully. Velocity is a distributed, shared cache and we run it across several servers in a clustered arrangement with failover and redundancy. Velocity: http://blogs.msdn.com/velocity/ Cache provider: http://nhcontrib.svn.sourceforge.net/viewvc/nhcontrib/trunk/src/NHibernate.Caches.Velocity/ Velocity /is/ a bit cranky (to be expected for a CTP) but when you master its nuances, it's a really nice and stable bit of kit. It should go RTM soon. Cheers, Chris. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
