Menu
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?
351
Distributed caches are especially useful in environments with high data volume and load. The distributed architecture allows incremental expansion/scaling by adding more computers to the cluster, allowing the cache to grow in step with the data growth.
The IDistributedCache interface provides the following methods to manipulate items in the distributed cache implementation: Get, GetAsync: Accepts a string key and retrieves a cached item as a byte[] array if found in the cache. Set, SetAsync: Adds an item (as byte[] array) to the cache using a string key.
Redis is an open-source in-memory data structure project implementing a distributed caching, in-memory key-value database. Redis supports different kinds of abstract data structures, such as strings, lists, maps, sets, sorted sets, hyper log, bitmaps, streams, and spatial indexes.
Velocity is a distributed cache designed specifically for the . NET platform. Many of the features will be recognizable to those familiar with other distributed in-memory caches. It is currently available as a community tech preview. There are two types of clients for Velocity.
Velocity was a codename while the product was in development, I don't think there was ever an intention from Microsoft to release a standalone product called Velocity. (Apart from anything else, there's already a Java product called Velocity).
AppFabric is the output of two development projects, Velocity and Dublin (which is workflow, not WCF).
Although the two parts share an installer, if you want the distributed caching parts of AppFabric you can just install them; you're not obligated to install the whole thing. I've circled the options you need to select in the installer for the distributed caching bits in red here, the WF bits in blue.
121
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
