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

Datastore Synchronicity Audit #139

Open
aschmahmann opened this issue Nov 11, 2019 · 0 comments
Open

Datastore Synchronicity Audit #139

aschmahmann opened this issue Nov 11, 2019 · 0 comments

Comments

@aschmahmann
Copy link
Contributor

aschmahmann commented Nov 11, 2019

This issue is a placeholder to keep track of which libp2p and IPFS components use Datastores and what level of synchronicity are required from the components.

This is in preparation for implementing #137 and switching the IPFS Badger implementation to have synchronous writes turned off by default.

If you know of any places where the datastore is used and where synchronicity may be required please either add in a comment or just modify this post below this line:


Adding Files to IPFS: Needs to synchronize after a single Add operation is complete
Removing Files from IPFS: No synchronization required (could be picked up in GC)
Pinning (Add + Remove) from IPFS: Required after each operation
IPNS Updates: Needs to sync after Put
DHT Record Updates: No?
Record Routing Updates: No?
Peerstore: No
Recording Metrics: Probably not

Filestore: ?
Badger: Just enable Sync if async flags is enabled
FlatFS: No
S3: No

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