Skip to content
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.

Make database layer pluggable #51

Closed
3 tasks
ukstv opened this issue Jul 7, 2017 · 2 comments
Closed
3 tasks

Make database layer pluggable #51

ukstv opened this issue Jul 7, 2017 · 2 comments

Comments

@ukstv
Copy link
Member

ukstv commented Jul 7, 2017

  • Move to PouchDB or LevelDB
  • Set database as a parameter
  • Ensure it still works in browser
@ukstv ukstv added this to the v2.0 Plug milestone Jul 7, 2017
emschwartz added a commit to emschwartz/machinomy that referenced this issue Jan 14, 2018
@emschwartz
feat: allow Engine to be passed in
33c714d 
probably a temporary measure, until machinomy#51 is done
ukstv pushed a commit that referenced this issue Jan 14, 2018
@emschwartz @ukstv
feat: allow Engine to be passed in
3532f49 
probably a temporary measure, until #51 is done
@emschwartz
Copy link
Contributor

Using levelup is nice because it abstracts away the differences between the underlying persistence layers and works with a number of different stores, including LevelDB, RocksDB, JSON files, memory-only, etc. Some of the stores are out of date and not compliant with the latest API, but I think that ecosystem has the best chance of having multiple working stores that use a common abstraction.

@emschwartz emschwartz mentioned this issue Jan 14, 2018
Open
@ukstv ukstv removed this from the v2.0 Plug milestone Jan 17, 2018
@ukstv
Copy link
Member Author

ukstv commented Apr 11, 2018

Closing as done. One could select between MongoDB, Postgres, NeDB now.

@ukstv ukstv closed this as completed Apr 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ukstv @emschwartz