---
title: "Comment by Daniele Maccari on \"Interface with one implementation?\nGive delegate a try!\" | Hashnode"
description: "Now this is an interesting approach. However, I wonder what would happen if you had some interface which is actually meant to represent a set of cohesive facets"
url: "https://hashnode.com/posts/interface-with-one-implementation-give-delegate-a-try/5f6f91fe5fd46b6601bbf96c/comment/63f29a789a615a95ce2edc61"
---

[Discussion](https://hashnode.com/posts/interface-with-one-implementation-give-delegate-a-try/5f6f91fe5fd46b6601bbf96c)

Comment [Interface with one implementation? Give delegate a try!](https://hashnode.com/posts/interface-with-one-implementation-give-delegate-a-try/5f6f91fe5fd46b6601bbf96c)

[Daniele Maccari](https://hashnode.com/@macco3k)

[Feb 19, 2023](https://hashnode.com/posts/interface-with-one-implementation-give-delegate-a-try/5f6f91fe5fd46b6601bbf96c/comment/63f29a789a615a95ce2edc61)

Now this is an interesting approach. However, I wonder what would happen if you had some interface which is actually meant to represent a set of cohesive facets of behaviour, i.e. a role proper. Would you consider that a proper abstraction? I also fail to see exactly how you would inject all those delegates into your high level component/use case/service/whatever. Would that not pollute it? Of course, that might be pointing to refactoring some these deps out into their own service. But then you're back at the beginning, ain't you?