What do you use for distributed caching in web farms with ASP.NET?

Question

I am curious what others are using in this situation. I know a couple of options that are there, for example, memcached port or ScaleOutSoftware. The memcached ports do not seem to be active (correct me if I am wrong). ScaleOutSoftware is too expensive for me (I have no doubt it's worth it). This does not mean that I do not want to hear about people using memcached or ScaleOutSoftware. I simply declare that I “know” at this stage.

So my question is basically this: for you from ACTIVELY , using distributed caching, what are you using, are you happy with this and what should I look for?

I will be switching to two servers very soon ... both will be in one place. I use caching quite heavily (but carefully) to reduce the load on my database server.

Edit: I downloaded the Scaleout Software solution. I encoded it and it seems to work very well. I just need to decide if my wallet will part with cash for it. :) Does anyone have good or bad results with ScaleoutSoftware?

Edit again: Has it been a little time since I asked about this? Any other thoughts on this? We ended up buying a solution from ScaleOutSoftware and were happy with it, but I'm curious what others are doing.

Answer 1

We are currently using an incredibly simple cache that I wrote in a couple of hours, based on re-placing the ASP.NET cache in the Windows service ( more information and source code here ). I will not pretend that it is approaching optimized, like something like Memcached, but we just looked for something simple and free until Velocity arrived, and it got up very well even with a rather heavy load.

It depends on our personal preferences regarding the main components, that is, those that affect the site’s accessibility or not, that they are either (a) supported by a provider with a history of fast and high-quality support, or (b) written by us to if something went wrong, we can fix it quickly. Open source is all good and good, and indeed we use some OSS, but if your site is offline, then, unfortunately, in newsgroups, etc. There is no 1 hour SLA, and only because OSS does not mean that you have the necessary understanding or ability to correct it yourself.

Answer 2

Microsoft has a product, code-named Velocity . It is still in CTP and moving slowly, but it looks like it will be very good. In the near future, we will beat him to understand how he is doing what we want to do (> 2 million read / write per hour). Will be published with the results.

Answer 3

There is a 100% proprietary .NET, well-documented open source project (LGPL) called the Shared Cache . It doesn't seem to be mentioned in SO yet, but it is promising and should be able to do what most people expect from a distributed cache. It even supports various strategies, such as distributed or replicated caching, etc.

I will update this message with more detailed information as soon as I have the opportunity to try it in a real project.

Answer 4

We use the memcached port for Windows, and we are very happy with that. The enyim.com memcached API is great and easy to use. It is also an open source, which is a great advantage if you ask me.

Now we use this setting in a web application for production, and this has helped to significantly improve productivity.

Answer 5

There is a great .NET shell / port found here on Codeplex. Awesomesauce!

Answer 6

We use memcached with the enyim library in a production environment (www.funda.nl). It works great, very satisfied, but we noticed a significant increase in CPU usage on clients. Presumably due to serialization / deserialization. We do about 1000 views per second.

Answer 7

One proven product of 100 customers worldwide NCache . His

multifunctional product that allows you to save session state in a redundant and affordable way, allows you to exchange data

within the enterprise, as well as binding for WAN sharing, acting as a data fabric, and finally, it allows you to create an elastic level of caching so that when

your application scales, you can add servers to the cache and actually improve performance.