Caching Code Location in a Domain Driven Design
问题 In an application that has followed a Domain Driven Design where you have the following sorts of concepts A repository that deals with the DataBase access A application service that co-ordinates interactions between enties and value objects etc. where in general would you put caching code to elimenate an expensive call to the database? I have seen code bases that just cache all over the place and it is difficult to monitor memory usage and difficult to provide guidelines to other developers.