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

Research projects - Figure out the backup for Cloudfare #475

Open
1 task
harshita-srivastava-yral opened this issue Dec 2, 2024 · 7 comments · May be fixed by yral-dapp/yral-backend-cloudflare-workers#4
Assignees

Comments

@harshita-srivastava-yral
  • Upload 1000 videos and try downloading it. Evaluate STORJ as a backup for cloudfare.
    Progress made so far:
  • 3 TB storage has been uploaded 4-5$ on STORJ
  • 3 Satellites are there and once its hit then it gives where the storage it done
  • 2 TB storage in cloudfare is expensive in terms of cost
  • Approach we want to take: Spin up the node on docker container and get them on fly
  • Today we have google cloud as secondary backup
  • Major deciding factor is going to be latency. We can also load balance between 2 networks and improve resilience of our systems
  • Decentralised network - Upload bandwidth required is more (1 MB requires 3 MB upload bandwidth)
  • If you run the render node, then you will have to do the upload of all. Make Gateway and send it to gateway then that does the upload., Then multiple upload is supported. Gateway provides S3 end points which we would need.
@harshita-srivastava-yral
Copy link
Author

@harshita-srivastava-yral to connect with @tushar-saxena-yral to create a ticket with sub issues around this

@tushar-saxena-yral
Copy link

tushar-saxena-yral commented Dec 2, 2024

Check out yral-dapp/hot-or-not-web-leptos-ssr#542 for an initial look on how storj will play out when used in the feed

@harshita-srivastava-yral
Copy link
Author

  • Fly machine looks like corrupted and hence offchain agent is down
  • @ravi-sawlani-yral Is looking into it. Once resolved, please communicate it over developers so that we can resume the issues dependent on it

@harshita-srivastava-yral
Copy link
Author

  • Storage credentials are left.
  • PR is left to be reviewed. @komal-sai-yral to help review the PR as he has most context to this

@harshita-srivastava-yral
Copy link
Author

  • Once the authorisation is required, @tushar-saxena-yral please tag this issue to @saikatdas0790 with the summary of authorisation details required
  • Keep the issue within the same repo

@harshita-srivastava-yral
Copy link
Author

@harshita-srivastava-yral
Copy link
Author

  • We are deferring this task for now as there is a blocker
  • Moving to PnD frontend integrations for now

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