repository pattern, heavily used in Entity Framework, which is a class has a repository field(normally injected by DI), so whatever you do save, delete,update a record, you let the repository instance do it like
_repository.delete("someID");
so isn't that the same thing that proxy pattern try to achieve? In proxy pattern, you also have a proxy instance, and let this instance does the job for you.
so what's the difference between proxy and repository pattern
Aucun commentaire:
Enregistrer un commentaire