DataStore question about android-clean-architecture-boilerplate HOT 8 CLOSED

The repository is meant for passing data to and from the domain layer whereas DataSources are for pure data operations. The way I see it a Repository has a one-to-many relation to DataSource hence the abstraction? That's just my opinion though.

from android-clean-architecture-boilerplate.

@anstaendig you got it wrong, i asked why there is DataStore, why not just DataSource

from android-clean-architecture-boilerplate.

Wait, am I mixing something up here? There's no such thing as a DataSource interface?! Can you clarify?

from android-clean-architecture-boilerplate.

In this pic, you can see it. In code, they should be BufferooCache and BufferooRemote
Why not this approach ?

from android-clean-architecture-boilerplate.

Ah, now I get it. I think the reason is that with one more layer of abstraction you have the freedom to implement the DataSources in different ways and then have one interface via the DataStore. With the approach you mentioned all DataStores have the same interface. The approach in here has the flexibility to have different interfaces for cache and data.

I hope I did not mix up things again but now it seems plausible :D

from android-clean-architecture-boilerplate.

With approach i mentioned, you only may have some empty methods in Local or Remote DataSource. But to overcome that, introducing one more abstraction and 2 different interfaces does not look attractive to me :)

from android-clean-architecture-boilerplate.

This is optional. If you have one interface shared between the cache and remote stores then you could end up having a lot of unused methods. The difference between the cache interface and the remote interface is quite a lot, meaning that they'd be a lot of unused bloat in the remote implementation class. THis is likely just personal preference though, no big deal what you go for either way :)

from android-clean-architecture-boilerplate.

Ok 👍

from android-clean-architecture-boilerplate.