I'm currently working on a project that require a web cache solution of the most robust nature to support very high usage rates.
I researched the web for such solutions and came across memcached and Shared Cache and now i need to decide.
My solution is with .Net so i prefer a native cache system with high performance but before i choose to work with SharedCache
i wanted to know if there are any uses of Shared cache in big web application on production that perform millions of cache set/get a day?
also, i wanted to ask, for what tasks do u mainly use shared cache other than just caching database queries?... session maybe?
I'm also trying to understand if there's a reason to use this cache provider? I had been using MemCached for a long time, and as it's built using C++ it's faster and can be hosted on cheap linux servers.
Also, there are some .net integration clients to replace the default session and cache providers, and can be configured as the NHibernate cache as well.
I don't wanna look as a big MemCached fan :), but it was also tested under real stress situations, like YouTube, LiveJournal, SourceForge, Facebook, and many others (http://en.wikipedia.org/wiki/Memcached)
So is there a reason to use it and don't use memcached?
Do you have a performance or feature comparision?
Jun 16, 2008 at 5:06 PM
Edited Jun 22, 2008 at 1:09 PM
Shalom Yaniv and hi Diego,
the main reason behind Shared Cache is easy, an open source solution which is written 100% in managed code. Sharedcache has a distributed and replicated mode and its FREE - doesn't matter how much cache nodes you need!
Memcache is a great solution as you have written already and I agree with you 200% and even more. Even then there are several companies, like Alachisoft, Tangasol (bought by Oracle), Scaleout Software and many more providers which have written
similar solutions already years ago but none of them were freeware, open source and developed in managed code. Some main reasons are listed within my blog entry: http://netrsc.blogspot.com/2008/02/indexusnet-shared-cache-11-reasons-why.html may
this help you to understand in which cases Shared Cache will assist your needs.
About your question around performance comparisons have a look at the following link: http://netrsc.blogspot.com/2008/02/shared-cache-compare-results-between.html the
results are not published but they are quite similar to those I had within my test-environment with memcached.
During development of http://www.indeXus.Net we had the need for this component and we developed it and made it available for the community because there was nothing free of charge available. At my work place we
use Shared Cache for a huge backend systems which is not comparable with any of your mention companies but I know that some companies around the world are using Shared Cache productive. Have a look at this link: http://www.sharedcache.com/cms/special_thanks.aspx
Since Microsoft comes out now with CTP1 of the project "Velocity" (a distributed and replicated caching system) we agreed internally to go on with Shared Cache at least as long as we know which licensing model Microsoft puts behind this
if you have further questions, feel free to contact me directly over sharedcache [at] indexus [dot] net