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.

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

Use concurrency in the data persistence layer? #214

Closed
carolynvs opened this issue Jun 2, 2020 · 1 comment
Closed

Use concurrency in the data persistence layer? #214

carolynvs opened this issue Jun 2, 2020 · 1 comment

Comments

@carolynvs
Copy link
Contributor

Right now our data persistence layer is designed without concurrency. There isn't an opportunity for the caller to introduce it either because our functions are controlling the looping mechanisms to retrieve lists of data, or child datasets. With #212 the number of claims in an installation, or outputs in a result, etc is large enough that allowing concurrency, or just using it inside our library is necessary.

So let's decide on it and make the improvement after #212 is merged.
This was referenced Jun 2, 2020
Open
Merged
@carolynvs
Copy link
Contributor Author

Closing since data persistence has been removed from cnab-go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@carolynvs