Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch from PouchDB to LokiJS #9

Closed
gschier opened this issue Apr 26, 2016 · 0 comments
Closed

Switch from PouchDB to LokiJS #9

gschier opened this issue Apr 26, 2016 · 0 comments

Comments

@gschier
Copy link
Contributor

gschier commented Apr 26, 2016

Why?

PouchDB required high storage overhead because it requires saving a full history of every document. If we don't necessarily need sync, this is not worth it.

LokiJS

LokiJS has a very similar API to PouchDB (probably simpler) so it should be trivial to drop in.

Wins

  • No longer have to debounce user input
  • Can use the NPM package
  • Can easily persist to file for Dropbox/cloud sync
  • Has a changes API that can be used to sync remotely
@gschier gschier added this to the v3.0 Launch milestone Apr 26, 2016
@gschier gschier added Improvement and removed Bug labels Apr 26, 2016
This was referenced Apr 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant