Purpose Of AppFabric Caching Services | AppFabric Interview Question | .Net Interview Question

One way to improve the performance and scalability of many applications is to speed up their access to data. With ASP.NET applications, for example, it’s easy to make the logic scale: just deploy multiple copies of that logic on multiple servers, then spread user requests across those servers. Improving this aspect of an application’s performance can be as easy as adding more servers.

But if all of those servers are relying on a single database server, access to data can quickly become a bottleneck. If an ASP.NET page has to wait to access the data it needs, adding more front-end servers won’t help. One option is to run the application’s database on a bigger machine. This can work, but there are limits: scaling up with bigger and bigger computers only goes so far, and it can get quite expensive. What’s needed is a way to scale out, making frequently accessed data available on multiple computers and thus getting away from a single-server bottleneck.

An effective way to do this is to create a distributed cache that spreads data across multiple machines. Rather than send every request to a single database server, the ASP.NET application can now access the data it needs from one of several different machines. The load is distributed, and the application will likely perform better. This is exactly what’s done by AppFabric Caching Services, as described next.