Temporal Nexus: Deploy to Production - Temporal Cloud & Nexus #3078
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
jsundai
commented
Sep 12, 2024
prasek
requested changes
Sep 13, 2024
| ### At-least-once Execution Semantics and Idempotency | ||
|
|
||
| Nexus Operations, like Activities, have at-least-once execution semantics. | ||
| The caller's Nexus Machinery will keep trying to start the Operation over and over, so the Nexus `Operation` handler should be idempotent just like Activities should be idempotent as a general rule. It's not required in all cases, but highly recommended in general. |
There was a problem hiding this comment.
Suggested change
| The caller's Nexus Machinery will keep trying to start the Operation over and over, so the Nexus `Operation` handler should be idempotent just like Activities should be idempotent as a general rule. It's not required in all cases, but highly recommended in general. | |
| The caller's Nexus Machinery will keep trying to start the Operation over and over until the ScheduleToClose timeout is exceeded which has a [maximum duration](/operations#limits??). This means the Nexus `Operation` handler should be idempotent just like Activities should be idempotent as a general rule. It's not required in all cases, but highly recommended in general. |
mastermanu
reviewed
Oct 1, 2024
| Calls across existing Namespaces can be enabled by creating a Nexus Endpoint in the Nexus API Registry, creating a Nexus Service in a Worker in the handler Namespace, and then using the Nexus Service from a caller Workflow in a different Namespace. | ||
|
|
||
| Monolithic Namespaces can be decomposed into multiple Namespaces, by hiding service implementations behind a Nexus Endpoint in the monolithic Namespace, pointing all consumers at the new Nexus Endpoint, and then changing the Endpoint’s target Namespace to a different Namespace. | ||
| Multiple Nexus Endpoints can target a single monolithic Namespace. |
There was a problem hiding this comment.
[Nit] "can target a single Namespace" --> I think monolithic is not needed for this line
mastermanu
reviewed
Oct 1, 2024
mastermanu
reviewed
Oct 1, 2024
mastermanu
reviewed
Oct 1, 2024
mastermanu
reviewed
Oct 1, 2024
mastermanu
reviewed
Oct 1, 2024
…lio/documentation into temporal-cloud-deploy-production
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.
What does this PR do?
Preview
Notes to reviewers
Anchors and links to be added later.