persistence might be useful for saving login information or information that would allow a web application to work offline. Client-side persistence is also useful for information relevant to having the page load quickly. i.e. widgets that will get run repeatedly on visits.
Obviously this is where you are going to store the hunk of your data for all your users, customers, locations, etc. Your local machine isn't going to store everyone's data every time. That would make no sense. You need an external storage center for data if you are using server-side persistence.
Stores data with no expiration date, and gets cleared only through JavaScript, or clearing the Browser cache / Locally Stored Data.
- It's there forever until we clear it or restart our computer.
The sessionStorage object stores data only for a session, meaning that the data is stored until the browser (or tab) is closed. Data is never transferred to the server.
- It's there until we close the browser.
Stores data that has to be sent back to the server with subsequent requests. Its expiration varies based on the type and the expiration duration can be set from either server-side or client-side (normally from server-side).
- It's there until it expires or is manually cleared.
Firebase offers an extremely easy to use system for relaying data between your application and their dedicated platforms.
It offers an easy to use, intuitive GUI for seeing your data in real-time.
It offers near instantaneous transmission of data between the Firebase database and your application. Of specific importance is the concept of "real-time" data binding (i.e. when your data changes in the database it will IMMEDIATELY reflect that change in your application.)