docs: add more orchestrator documentation #346
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Romain Goussault <[email protected]>
ThibaultFy
reviewed
Aug 21, 2023
Co-authored-by: ThibaultFy <[email protected]>
Co-authored-by: ThibaultFy <[email protected]>
Signed-off-by: Romain Goussault <[email protected]>
Signed-off-by: Romain Goussault <[email protected]>
Signed-off-by: Romain Goussault <[email protected]>
|
|
||
| Distributed orchestration enables trustless verification of the integrity of assets (functions, model, data), but it requires connections between organizations, and introduces a network overhead. It's not possible to upgrade a Substra network when using distributed orchestration. | ||
|
|
||
| On the other hand, centralized orchestration requires trust in the central server, but it is more efficient, faster and easier to deploy and maintain. |
There was a problem hiding this comment.
Not sure that the meaning of efficient is straightforward in this case
There was a problem hiding this comment.
I removed it.
|
|
||
| On the other hand, centralized orchestration requires trust in the central server, but it is more efficient, faster and easier to deploy and maintain. | ||
|
|
||
| As long as you trust whomever is operating the orchestrator DB not to tamper with it, both modes offer the same level of guarantees. The decentralized mode has nice theoretical guarantees, but the network overhead is very significant, and has a lot of operational drawbacks. That is why, the vast majority (if not all) of the Substra deployments are using the centralized orchestration system as it is easier to operate and faster. However, the distributed orchestration is still maintained. |
There was a problem hiding this comment.
That is why, the vast majority (if not all) of the Substra deployments
Should we emphazise that is the current situation but historically it may have been different ? (i.e. That is why, the vast majority (if not all) of the current Substra deployments)
There was a problem hiding this comment.
agree, added
Co-authored-by: Guilhem Barthés <[email protected]>
Signed-off-by: Romain Goussault <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Romain Goussault [email protected]