Hi everyone, Recently I had tried to implement Koi...

# koin-contributors

[bobby]

Hi everyone,
Recently I had tried to implement Koin in my project. After trying Koin, I realized how concise and simple the implementation is. The time for me to learn using Koin is pretty fast, comparing to Dagger 2. But there's something that keeps bothering me. I saw an article mentioned that Koin isn't using the DI pattern, rather it using the Service Locator pattern. My question is, why Koin use the Service Locator pattern? And is that matter which pattern to use? Thanks a lot.

[arnaud.giuliani]

Koin is a DI framework in the sense that it allows you to constructor injection

[arnaud.giuliani]

the main subtile thing is that, people only see one thing by inject()

[arnaud.giuliani]

this is the key of Koin, to unlock the service locator pattern to something that is smarter to write than a lateinit var injected property

[arnaud.giuliani]

the thing is, a by inject() will actively request the API to look at your instance

[arnaud.giuliani]

With dagger, your manually ask Dagger to inject your properties

[arnaud.giuliani]

but then, the drawback is that your property is linked to Koin directly, contrary to Dagger

[arnaud.giuliani]

but ...

[arnaud.giuliani]

this is only affecting Android classes (Activity/Fragment) that you can’t create directly by hand

[arnaud.giuliani]

perhaps my talk about Koin can help you: https://www.droidcon.com/media-detail?video=390453576

[bobby]

I'll listen to the talk and think about your answers thoroughly, thanks