Menu
I have couple of questions about Repository pattern:
If I'm using only offline database for example Room with LiveData is there any use of Repository pattern?
If my app is offline right now, but will be connected to remote db in the future should I implement repository pattern or it's not going to be a problem to do it later?
292
The repository pattern is a design pattern that isolates the data layer from the rest of the app. The data layer refers to the part of your app, separate from the UI, that handles the app's data and business logic, exposing consistent APIs for the rest of your app to access this data.
The Repository pattern. Repositories are classes or components that encapsulate the logic required to access data sources. They centralize common data access functionality, providing better maintainability and decoupling the infrastructure or technology used to access databases from the domain model layer.
MVVM stands for Model, View, ViewModel. Model: This holds the data of the application. It cannot directly talk to the View. Generally, it's recommended to expose the data to the ViewModel through Observables. View: It represents the UI of the application devoid of any Application Logic.
The Repository pattern is used to decouple the business logic and the data access layers in your application. The data access layer typically contains storage specific code and methods to operate on the data to and from the data storage.
To begin with, Repository pattern have nothing to do with technology or programming language.
Repository pattern is useful to separate persistence concerns from rest of the application. This also helps improve testing ability because now, you can mock the Repository and test rest of the code easily without connection to persistence layer.
If I'm using only offline database for example Room with LiveData is there any use of Repository pattern?
I am not aware about those technologies. But as said above, purpose of repository is ignorance of persistence. No matter what your data store is (in memory database, RDBMS, Excel/CSS, Web service, XML, JSON or whatever), repository pattern helps abstracting it. So yes, repository pattern is helpful here.
If my app is offline right now, but will be connected to remote db in the future should I implement repository pattern or it's not going to be a problem to do it later?
In fact, I will strongly recommend implementing repository here. As the persistence is ignored, your rest of the application can be easily designed based on assumption that data will be available/persisted SOMEHOW (local in case of offline and server in case of future) without even knowing it is offline or online. That way, when in future you shift from local store to remote store, your application does not affect in any way as it is build against repository interfaces and those interfaces does not change. Persistence concern is fully handled by Repository now.
My other answer may be helpful.
87
IMO
Yes, its useful to abstract how the data is stored so you have the flexibility to respond to changes both known and unknown.
It will require refactoring. I think it depends on details of your app and how large it is.
23
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
