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

decouple from mongo #48

Open
facundoolano opened this issue Apr 20, 2015 · 1 comment
Open

decouple from mongo #48

facundoolano opened this issue Apr 20, 2015 · 1 comment

Comments

@facundoolano
Copy link
Member

Make the code generic enough so a new db backend can be implemented without having to modify the invisible code.

@facundoolano
Copy link
Member Author

An interesting way of doing this would be to let the different db backends define what operations can be done with the invisible models. For example, mongo might define find and findById, while elasticsearch would have things like search and suggest.

We could then have packages like invisible-mongo and invisible-elasticsearch, and this one would be just in charge of generating the proper REST endpoints and exposing to the client whatever API the db backend defines.

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