Comments on: Digipede + Velocity

By: Sarah On Distributed Caching

Sarah On Distributed Caching — Wed, 05 Nov 2008 11:00:45 +0000

Thanks for the great piece of advise Rob. We are indeed trying to introduce new things into our product and will continue to push the limit.

We just came out with a new version (NCache 3.4) that has many new features that are cutting edge. Many more are on the drawing board and YES, we are planning on providing a compatible API. No code change would be required at all.

Cheers,

Sarah.

By: Robert W. Anderson

Robert W. Anderson — Tue, 04 Nov 2008 18:20:32 +0000

Thanks for the comment — even if it is a product plug.

There is no doubt that Microsoft has a long way to go to catch up with the established cache vendors, including Alachisoft. Your job, of course, is to continue to innovate ahead of Microsoft.

I suggest that you — as much as possible — provide an alternative API that is Velocity-compatible. People will adopt Velocity, and you want to make it easy to switch. A compatible API will allow the adopters of Velocity to upgrade to your solution with minimal changes. If you do it right, you may be able to make it a config-only change.

By: Sarah On Distributed Caching

Sarah On Distributed Caching — Tue, 04 Nov 2008 14:34:02 +0000

Although Velocity has made progress from CTP1 to CTP2, it still leaves much to be desired. It will be some time before they provide all the important features in a distributed cache and even longer before it is tested in the market. I wish them good luck. In the meantime, NCache already provides all CTP2 & V1, and many more features. NCache is the first, the most mature, and the most feature-rich distributed cache in the .NET space. NCache is an enterprise level in-memory distributed cache for .NET and also provides a distributed ASP.NET Session State. Check it out at Distributed Cache. NCache Express is a totally free version of NCache. Check it out at Free distributed Cache.