Clean Architecture Repository
up vote
2
down vote
favorite
Building an application using Google recommended architecture seem like a nice way of separation and modularization for the app. That being said, I often stumble upon the fact that, when caching data that comes from an API, a need for using different models for remote & local dataSources may arise. (I found a comment here by swankjesse which states the same).
Different models looks nice, but having complex models with multiple nesting levels seems to be a pain in the ass (mapping local & remote models to a common data layer entity).
Another argument would be that when requesting data from network, API may respond with a JSON mapping pagination and other stuff inside (which is needed by ViewModel(just an example) to load more data).
Having a Repository with local & remote dataSources looks like is kinda ruined (local responds with List of Objects, remote responds with class that contains the List of Objects).
All sample apps that I've seen demonstrates using simple POJOs (which in production code is almost never realistic).
Any idea on solving this architecture puzzle?
android repository 
android-architecture-components clean-architecture asked Nov 14 at 9:49
DoruAdryan
81311731
add a comment |
up vote
2
down vote
favorite
Building an application using Google recommended architecture seem like a nice way of separation and modularization for the app. That being said, I often stumble upon the fact that, when caching data that comes from an API, a need for using different models for remote & local dataSources may arise. (I found a comment here by swankjesse which states the same).
Different models looks nice, but having complex models with multiple nesting levels seems to be a pain in the ass (mapping local & remote models to a common data layer entity).
Another argument would be that when requesting data from network, API may respond with a JSON mapping pagination and other stuff inside (which is needed by ViewModel(just an example) to load more data).
Having a Repository with local & remote dataSources looks like is kinda ruined (local responds with List of Objects, remote responds with class that contains the List of Objects).
All sample apps that I've seen demonstrates using simple POJOs (which in production code is almost never realistic).
Any idea on solving this architecture puzzle?
android repository android-architecture-components clean-architecture asked Nov 14 at 9:49
DoruAdryan
81311731
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Building an application using Google recommended architecture seem like a nice way of separation and modularization for the app. That being said, I often stumble upon the fact that, when caching data that comes from an API, a need for using different models for remote & local dataSources may arise. (I found a comment here by swankjesse which states the same).
Different models looks nice, but having complex models with multiple nesting levels seems to be a pain in the ass (mapping local & remote models to a common data layer entity).
Another argument would be that when requesting data from network, API may respond with a JSON mapping pagination and other stuff inside (which is needed by ViewModel(just an example) to load more data).
Having a Repository with local & remote dataSources looks like is kinda ruined (local responds with List of Objects, remote responds with class that contains the List of Objects).
All sample apps that I've seen demonstrates using simple POJOs (which in production code is almost never realistic).
Any idea on solving this architecture puzzle?
android repository android-architecture-components clean-architecture asked Nov 14 at 9:49
DoruAdryan
81311731
Building an application using Google recommended architecture seem like a nice way of separation and modularization for the app. That being said, I often stumble upon the fact that, when caching data that comes from an API, a need for using different models for remote & local dataSources may arise. (I found a comment here by swankjesse which states the same).
Different models looks nice, but having complex models with multiple nesting levels seems to be a pain in the ass (mapping local & remote models to a common data layer entity).
Another argument would be that when requesting data from network, API may respond with a JSON mapping pagination and other stuff inside (which is needed by ViewModel(just an example) to load more data).
Having a Repository with local & remote dataSources looks like is kinda ruined (local responds with List of Objects, remote responds with class that contains the List of Objects).
All sample apps that I've seen demonstrates using simple POJOs (which in production code is almost never realistic).
Any idea on solving this architecture puzzle?
android repository android-architecture-components clean-architecture android repository android-architecture-components clean-architecture asked Nov 14 at 9:49
DoruAdryan
81311731
asked Nov 14 at 9:49
DoruAdryan
81311731
asked Nov 14 at 9:49
DoruAdryan
81311731
asked Nov 14 at 9:49
DoruAdryan
81311731
asked Nov 14 at 9:49
DoruAdryan
81311731
81311731
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53297243%2fclean-architecture-repository%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
