Refactor data layer for non-persistence scenario

xMartin / grouptabs

Mobile Web App to organize payments in dynamic groups of people.

https://grouptabs.net

GNU General Public License v3.0

42 stars 11 forks source link

Refactor data layer for non-persistence scenario #167

Closed xMartin closed 4 years ago

xMartin commented 4 years ago

With the fix for #125 (5cabfcb) we introduced PouchDB memory adapter, which just adds an unnecessary memory cache.

With this approach we can support the current architecture of the data layers:

Remote database (PouchDB HTTP)
Local database (PouchDB IndexedDB, resp. Memory)
Memory (Redux)

But having two memory caches doesn't add value (but ~50KB in size), so we should refactor the architecture so that the local data layer is optional.

xMartin commented 4 years ago

Actually it does add value, which is a much better experience with bad connectivity. Temporary connection issues will be handled nicely with syncing whenever connected. The user should just not leave the page or refresh...