NW.js provides many ways to handle data persistence. You can obviously rely on a Node.js persistent database, such as EJDB, locallyDB, NeDB, or LowDB, but in this chapter, we're going to see how we can save and access persistent data by leveraging some of the latest browser storage technologies.
Note
I will not dwell on HTML5 Application Cache as I find its use to be pointless in a NW.js application; however, if you need to implement offline navigation, you know you can rely on it as well.
Web storage is a browser technology, which was once part of the HTML5 specification but lately split into its own specification, used to store temporary or permanent key-value data on the client side. It's by far the easiest way to achieve data persistence in the browser but also one of the weakest. Let's see some disadvantages of web storage:
Maximum 5 MB storage limit
Web storage calls are synchronous and can block the main document from rendering
As web storage writes...