> I would need to start storing them in a "traditional" database, introducing additional layers, serialization, overhead and bugs. If the app state is stored i

> I would need to start storing them in a "traditional" database, introducing additional layers, serialization, overhead and bugs. If the app state is stored in a single atom, I would use localForage[1] (available as a cljsjs package[2]) to keep it in sync between web workers and the main thread. It would also make the app accessible offline. [1] https://github.com/localForage/localForage https://github.com/localForage/localForage [2] https://clojars.org/cljsjs/localforage https://clojars.org/cljsjs/localforage