Differences of Data Caching and SQL Cache dependancy

See more:

ASP.NET

There are a few things that I would like to know - What are the differences of Data Caching and SQL Cache dependancy.

We had implemented the SQL Cache dependancy in our last project but had to discontinue it due to the reasons mentioned above as due to notifications some of the transactions were very slow.
Currently I am designing a framework for my client and I have implemented Data caching.

The problem with this feature is that, currently I am doing a POC on a single Web Server, but the application has to be deployed on the proper multi server environment (maybe web farm). If I am using Data caching then it doesnt help as multiple users would access the same cache, and if cache is invalidated, then the data would be inconsistent for some users. One approach is attaching the SessionID (UserID) with the Cache object for each user, but then if you have more number of concurrent users then I think it is not advisable to have this feature as the Server would become very heavy.

I read an article on Velocity, but cannot implement that for a POC.

Kindly suggest.

Thanks in advance.