Hi,
there are a lot of information inside the MonoX manual regarding the Caching mechanisms MonoX uses, but let me answer all of your questions and summarize everything.
1. Does Caching of monox extends any ASP.net caching architecture or is it pure custom.
Both, basically it extends standard
ASP.NET Caching and API signature is almost the same, the only thing that us purely custom is the "wrapper" layer above the caching used to allow caching provider pattern implementation.
2. Dooes Monox saves cahing data in memory or in file system.
This depends on the chosen provider, but by default MonoX uses memory provider which is
ASP.NET Caching.
3. What all types of caching does MonoX offers
Here is a list of providers and note that you don't need a lot of effort to build your own:
-
Memory Cache Provider (ASP.NET Caching)
-
AppFabric Cache Provider
-
Azure Cache Provider
-
Couchbase Cache Provider
4. When does Cache gets invalidated.
There are few actions that trigger cache invalidation: cache simply expires, you manually remove something from cache or some action inside the MonoX triggers cache invalidation (e.g. you post to forum then MonoX invalidates the user rating cache)
5. We have deployed MonoX in Load Balancer Environment does current architecture of caching supports this environment.
Yes, as I mentioned you can chose from on of the caching providers that you prefer. Bottom line is that you need to pull out caching storage out of the process, same applies for Session state and ViewState optimization used by MonoX (all of them are provider based so you can do the same as with cache).
Let us know if you need anything else.
Regards