<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: A readymade caching solution for scalable .Net applications</title>
	<atom:link href="http://www.nagarro.com/blog/shared-cache/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nagarro.com/blog/shared-cache/</link>
	<description>Nagarro blog: software development, design, architecture and usability</description>
	<lastBuildDate>Fri, 30 Jul 2010 13:51:47 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: william</title>
		<link>http://www.nagarro.com/blog/shared-cache/comment-page-1/#comment-524</link>
		<dc:creator>william</dc:creator>
		<pubDate>Wed, 17 Mar 2010 11:21:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.nagarro.com/blog/?p=133#comment-524</guid>
		<description>Hi Vikas,

Thanks for this post! The best way to achieve scalability and high performance is by using distributed .NET caching solution. There are many third party distributed caching solution are available in the market and you yourself has mentioned a few in this post. I also got a chance to use of the caching solution called &lt;a href=&quot;http://www.alachisoft.com&quot; rel=&quot;nofollow&quot;&gt;NCache&lt;/a&gt; by Alachisoft. After evaluating this product, my first impression was it is godsend for my app. The thing which I like most about NCache is its wide range of topologies. I recently came to know that they had also released the appliance for Memcached as well. if anybody is interested in it, can also download free version of NCache called as NCache Express.</description>
		<content:encoded><![CDATA[<p>Hi Vikas,</p>
<p>Thanks for this post! The best way to achieve scalability and high performance is by using distributed .NET caching solution. There are many third party distributed caching solution are available in the market and you yourself has mentioned a few in this post. I also got a chance to use of the caching solution called <a href="http://www.alachisoft.com" rel="nofollow">NCache</a> by Alachisoft. After evaluating this product, my first impression was it is godsend for my app. The thing which I like most about NCache is its wide range of topologies. I recently came to know that they had also released the appliance for Memcached as well. if anybody is interested in it, can also download free version of NCache called as NCache Express.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Atul Verma</title>
		<link>http://www.nagarro.com/blog/shared-cache/comment-page-1/#comment-341</link>
		<dc:creator>Atul Verma</dc:creator>
		<pubDate>Thu, 25 Jun 2009 15:14:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.nagarro.com/blog/?p=133#comment-341</guid>
		<description>Microsoft Project Code Named - “Velocity” 

“Velocity” is a distributed in-memory cache that provides .NET applications with high-speed access, scale, and high availability to application data.

* Caches any serializable CLR object and provides access through simple cache APIs.
* Supports enterprise scale: tens to hundreds of computers.
* Configurable to run as a service accessed over the network or run embedded with the application.
* Supports common cache configurations.
* Supports dynamic scaling by adding new nodes.
* Configurable number of backup copies to provide high availability.
* Automatic load balancing.
* Integration with administration and monitoring tools such as ETW, System Center, etc.
* Provides tight integration with ASP.NET to be able to cache ASP.NET session data in the cache without having to write it to source databases. It can also be used as a cache for application data to be able to cache application data across the entire Web farm.
* Follows the cache-aside architecture (also known as Explicit Caching) for V1. That is, you must decide explicitly which objects to put/remove in your applications and “Velocity” does not synchronize with any source database automatically.
* Support for multiple client languages (for example, PHP, C#, C++, etc.).

For more info visit http://msdn.microsoft.com/hi-in/library/cc645013(en-us).aspx</description>
		<content:encoded><![CDATA[<p>Microsoft Project Code Named &#8211; “Velocity” </p>
<p>“Velocity” is a distributed in-memory cache that provides .NET applications with high-speed access, scale, and high availability to application data.</p>
<p>* Caches any serializable CLR object and provides access through simple cache APIs.<br />
* Supports enterprise scale: tens to hundreds of computers.<br />
* Configurable to run as a service accessed over the network or run embedded with the application.<br />
* Supports common cache configurations.<br />
* Supports dynamic scaling by adding new nodes.<br />
* Configurable number of backup copies to provide high availability.<br />
* Automatic load balancing.<br />
* Integration with administration and monitoring tools such as ETW, System Center, etc.<br />
* Provides tight integration with ASP.NET to be able to cache ASP.NET session data in the cache without having to write it to source databases. It can also be used as a cache for application data to be able to cache application data across the entire Web farm.<br />
* Follows the cache-aside architecture (also known as Explicit Caching) for V1. That is, you must decide explicitly which objects to put/remove in your applications and “Velocity” does not synchronize with any source database automatically.<br />
* Support for multiple client languages (for example, PHP, C#, C++, etc.).</p>
<p>For more info visit <a href="http://msdn.microsoft.com/hi-in/library/cc645013(en-us).aspx" rel="nofollow">http://msdn.microsoft.com/hi-in/library/cc645013(en-us).aspx</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
