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

NATS Object Store as Source and Publisher storage #3742

Open
HeCorr opened this issue Mar 30, 2024 · 1 comment
Open

NATS Object Store as Source and Publisher storage #3742

HeCorr opened this issue Mar 30, 2024 · 1 comment
Labels
request/needs-discussion Request: Requires further discussion to proceed

Comments

@HeCorr
Copy link

HeCorr commented Mar 30, 2024

Since this project is now embracing NATS I believe it would be quite interesting to see added support for NATS Object Store, eliminating the need to setup an S3 server which could greatly simplify small projects that use Bacalhau.

However, keep in mind that Object Store is still in Experimental Preview.

@wdbaruni
Copy link
Collaborator

Hey @HeCorr, thanks for the suggestion. How do you see NATS Object Store fit in a bacalhau network?

Today we are embedding NATS servers within the requester/orchestrator nodes. An option would be for the requesters to host the object store, but I'll be concerned about adding an additional and heavy responsibility to the orchestrators

Another option would be to add a separate cluster of NATS servers to form their own RAFT group to replicate and store the objects. Kind of a super cluster of two cluster types, one for orchestration and others for storage. Though I am not sure if this can actually work and if NATS will route get and put requests across clusters.

What are your thoughts?

@wdbaruni wdbaruni added the request/needs-discussion Request: Requires further discussion to proceed label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
request/needs-discussion Request: Requires further discussion to proceed
Projects
Status: Inbox
Development

No branches or pull requests

2 participants