Leaky abstraction by omission

added by DotNetKicks
4/26/2021 3:34:19 PM

755 Views

Sometimes, an abstraction can be leaky because it leaves something out. Consider the following interface definition. What's wrong with it? Perhaps you think that the name is incorrect; that this really isn't an example of the Repository design pattern, as it's described in Patterns of Enterprise Application Architecture.


0 comments