343 Views
Second Level Caching is not one of the out-of-the-box features in Entity Framework. One of the great benefits of the EF is its ability to automatically generate database persistence commands (inserts, updates and deletes) based on the state information found in the context. But if that state information is unavailable, the EF has nothing to do when it’s time to call SaveChanges. Second-level caches are instrumental in solving this type of problem.
I think that what's even more valuable than the actual code she's written is the discussion of how to implement caching in an ORM, and the link here http://queue.acm.org/detail.cfm?id=1394141 discussing the implementation issues with any ORM cache.