Hi everyone. <https://github.com/gastsail/Cocktail...

# announcements

[Ayden]

Hi everyone.
https://github.com/gastsail/CocktailApp/tree/master/app/src/main/java/com/g/tragosapp/domain
According to this repo, the developer extract the interface and the actual implementation to different files.
Does this approach has any name?

[Vampire]

Good design? :-D

[Vampire]

"Coding to interfaces" is one of the phrases describing it partly

[Vampire]

You can easily swap the implementations if you just used the interfaces, like List vs. ArrayList , LinkedList, ...

[Zach Klippenstein (he/him) [MOD]]

I don't know if there's a name for specifically putting the interface and implementation in different files. But I've heard the pattern of logically separating the code called simply "the interface/impl pattern". But it also relates to other patterns such as dependency inversion.

[Ayden]

I see. Thank you @Vampire @Zach Klippenstein (he/him) [MOD]

[Ayden]

@Vampire not sure if this is a good design or not. But I heard from other it helps on creating test case.

[Vampire]

It can, as I said. If you stick to interfaces, you can easily swap implementations and then for example give a mock instead that implements the same interface.

[Ayden]

@Zach Klippenstein (he/him) [MOD] I found the name of this pattern. Bridge pattern.
https://en.wikipedia.org/wiki/Bridge_pattern

[Vampire]

Not really. Did you actually read the book, or the wiki page?

[Ayden]

@Vampire yeah. I actually read the short description and went through the SO to understand it.

Am I missing something?

[Vampire]

Yes, read it again. :-)
The wiki article explains it better than I could.