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.

Sign up for GitHub

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

Jump to bottom

Move persistence code into separate resource #12

Closed

Marak opened this issue May 23, 2013 · 1 comment

Member

Marak commented May 23, 2013

The persistence code should be kept in a separate resource.

Ideally, every different type of datasource would be a separate resource ( couch, redis, etc ) acting as an adapter to the persistence resource.

This would allow us to remove JugglingDB vendor from resource core, and put it into the persistence resource instead.

The text was updated successfully, but these errors were encountered:

Marak mentioned this issue

refactor [datasource] resource into [persistence] resource bigcompany/resources#32

Open

Marak mentioned this issue

Migrate all non-core resource code into new resources: [logger], [schema], [persistence] #16

Closed

Member Author

Marak commented Jun 13, 2013

Published with v0.4.1

Marak closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment