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

W3name publishing - Use a queueing system which can scale #66

Closed
adamalton opened this issue Aug 17, 2022 · 3 comments
Closed

W3name publishing - Use a queueing system which can scale #66

adamalton opened this issue Aug 17, 2022 · 3 comments
Assignees

Comments

@adamalton
Copy link
Contributor

adamalton commented Aug 17, 2022

Currently all w3name record requests are stored in memory before they are processed by the POST api end point to publish on the DHT. At the current traffic this is perfectly acceptable, but at a certain scale or volume of requests, this might cause the service to fall over.

@mbommerez mbommerez changed the title Use a queueing system which can scale W3name publishing - Use a queueing system which can scale Aug 25, 2022
@joshghent
Copy link
Contributor

joshghent commented Aug 31, 2022

@francois-potato to work on a proposal for this work.
Suggested implementation is to use SQS with a FIFO queue.
Using this tool: https://github.com/bbc/sqs-consumer

@francois-potato francois-potato self-assigned this Sep 5, 2022
@mbommerez
Copy link

@adamalton
Copy link
Contributor Author

This ticket is really in the wrong project. I've made a replacement ticket in ipns-publish, which is where it belongs: web3-storage/ipns-publisher#8

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

No branches or pull requests

4 participants