c# - Caching a Dynamic Portal -

currently working on large portal website , information shows user specific.now experiencing performance issues , have address possible number of users keep increasing.i heard caching in mvc4 , want know how effective in dynamic sites portal , kind of caching method should adopt.is there chance of backfire ?

in general important understand caching bringing resources closer consumer

in order choose caching method use, should analyze portal potential bottlenecks.

if example, bottleneck remote database - use local database runs on same machine portal (embedded data base/ in memory storage / key-value storage , etc.) or using session cache user data - in case resource consumer mvc application.

in 1 of our projects, had similar issue describing in question. in case bottleneck remote database, implemented sessionstate provider redis db (we couldn't use default session provider because of load ballancer) , solved issue us.

another caching may performed bring data closer end user - in case use mvc outputcache cache data on client side, server side, proxy or of them together.

something learned own mistakes - don't try solve issue not yet existing - can spend month trying implement complex caching solutions setting local high-performance database synchronizes remote one... there won't performance issues on particular application level.

if application architecture correct allow add caching later without major implications. suggest spend resources on correct application design , implementation.