Why did Microsoft get rid of Velocity Distributed Cache as standalone product?

I heard about Velocity several years ago when MS made a splash going head to head with MemCached.

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

I am a little worried, that this will impact how quickly MS can release new features/improvements for Velocity, now that it is a part of much bigger package.

Why did MS get rid of standalone version of Velocity, after all the effort they spent promoting it?

6
задан pnuts 26 October 2015 в 03:37
поделиться