Nuestro buen amigo Javier Caceres nos comparte su artículo:

Where do I place my Cache Layer?

You can virtually place your Cache access operations (read/write) wherever you have data, but in order to design modular and maintainable software it’s a good idea to centralize these operations into a separate layer to encapsulate and prevent ripple effect when changing the underlying provider (imagine that you start using Memcached, however your design should be good enough to allow a migration to somewhere like AppFabric Caching Service). Now the question is: where does exactly in my design fit the Cache layer?

The worst answer I can think of it’s replying with only one possibility. As a software Designer/Architect you should consider many scenarios and chose the best. Avoid facing your design decisions with a golden hammer / silver bullet. A common poor answer is placing the Cache layer between your Business and Data Layers. Another common answer is placing it between the Data Layer and the underlying data store.


Ver más aquí.

Fernando García Loera (Community Program Manager – Latin America Region)

Icono Ferglo 40x116twitter 40x40RSS 40x40facebook 40x116linkedin40x40xbox 40x40

Que es un MVP? / Tips para ser MVP