architecture and distributed caching thoughts in combination with indeXus.Net SharedCache - Part 2

SharedCache thought no 1: Define a clear delineation for the cache responsibility

You could e.g. define to use caching in your model within your DAO**, where the cache holds the object value. The goal is to ensure that all accesses are served from SharedCache instead of your RDBMS*. The access latency to SharedCache will be some 0.001 sec. while your call to the RDBMS* can take up to 0.050 sec. - it does not seems to make much difference but while we are talking about scalable systems - here the changes starting.

------------------

Download your copy of SharedCache: http://www.sharedcache.com
SharedCache will soon release session provider, which will assist you to work with SharedCache and ASP.Net Sessions.

Soon i will add some additional thought about how to provide optimistic transactional handling with SharedCache.

SharedCache is free and open source the only way you can see exactly what happens within your application.

* - RDBMS - relational database management system
** - DAO - Data Access Objects