Why did Microsoft get rid of the distributed Velocity cache as a standalone product?

Question

I heard about Velocity a few years ago when MS made a splash heading toward MemCached.

Recently, I needed to try which solution would work best in my project: MemCached or .NET Velocity. It took me a while to find Velocity again. It seems that MS has combined Velocity with some WCF tools, and now it is called AppFabric.
http://msdn.microsoft.com/en-us/windowsserver/ee695849

I'm a little worried that this will affect how quickly MS can release new features / improvements for Velocity, now that it's part of a much larger package.

Why did MS get rid of the standalone version of Velocity, after all the efforts they put into promoting it?

Answer 1

Velocity was a code name, while the product was under development, I do not think that there was ever any intention from Microsoft to release a stand-alone product called Velocity. (Among other things, there is already a Java product called Velocity ).

AppFabric is the result of two development projects: Velocity and Dublin (this is a workflow, not WCF).

Although these two parts are shared by the installer, if you want AppFabric distributed caching parts you can just install them; You are not required to install all of this. I have combined the options that you need to select in the installer for the distributed caching bits here in red and the WF bit in blue.