CODEWITHSUNDEEP
javascriptangular
Novark
Novark

Reputation: 419

What is the correct way of storing application data in an Angular 2.0 app?

In learning Angular 2, I've seen multiple examples where application data is stored in services.

For example: in a todo-list app, you'd find a "todo" service that would define a "todo entries" list that would become accessible to any consumer of that service.

My question is: Is there a better way of defining application data? Should it be separated from services?

In my particular case, I'd like to make use of localstorage to save a bunch of application data. Eventually, I might refactor this to instead save and load data from a database. Would it make more sense for me to be creating some sort of "data-storage" service that could be used by other services to save and retrieve data, or should data always live with the service that uses it? How might one choose to structure this in the "todo" example above?

Upvotes: 0

Views: 439

Answers (1)

Günter Zöchbauer
Günter Zöchbauer

Reputation: 657038

LocalStorage is only for improving user experience (caching for speed, or similar) but it's not a place to persist data that must not be lost. For this case you need a server where you can send the data to and which stores it in a database. https://www.firebase.com/ might be convenient for a start.

It is a good idea to separate data from the service that fetches or persists these data. If you use Angulars Http service to fetch and persist data from/to a server, this might be separation enough though. When your application becomes more complex you probably want more abstraction but this would need a more concrete example of what you actually try to accomplish.

Upvotes: 1

Related Questions