---
title: "Comment by Davide Bellone on \"Code Smell 135 -  Interfaces With just One Realization\" | Hashnode"
description: "What do you think of interfaces implemented by only one class, when that class represents a Service and not a DTO? Something like public interface IDoSomething"
url: "https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45/comment/628f273719bda58ac7fb25d7"
---

[Discussion](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45)

Comment [Code Smell 135 - Interfaces With just One Realization](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45)

[Davide Bellone](https://hashnode.com/@davidebellone)

[May 26, 2022](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45/comment/628f273719bda58ac7fb25d7)

What do you think of interfaces implemented by only one class, when that class represents a Service and not a DTO?

Something like

```
public interface IDoSomething{
void Do();
}

public class DoSomething : IDoSomething{
void Do();
}
```

[Maxi Contieri](https://hashnode.com/@mcsee)

[May 27, 2022](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45/comment/628f273719bda58ac7fb25d7#reply-62914931d97f80b5091d82ee)

IDoSomething is a name problem. I've never seen an IDoSomething in real world. I assume it is a _bad_ convention.

If this a service provided as an API interface for other systems it might suit the Exceptions scenario.

If it is for internal use is a code smell on premature generalization
