@indvinoth I’d also add that on a more conceptual level it’s breaking the separation of concerns and could cause problems down the road. Essentially it’s a bad design compromise. The model is just supposed to define how your data should be represented. So it’s “concern” is just saying "here is a collection of attributes and their types, and it is named ". You can have computed properties on a model which can transform the data a little bit or format it differently but in generally your model should just be a blueprint for some data. That means a model should never do data fetching or rendering or other things that are outside its limited realm of responsibility. A model should never be aware of the global application state, or really any state outside of itself, and a service usually represents some kind of global app state.