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. |
| 3. Update the Nexus Endpoint target to the new Namespace. | ||
| 4. Configure the Endpoint allowlist to allow calls from the original monolithic Namespace. | ||
| 5. New Nexus Operations will be routed from callers in the monolithic Namespace to the new Namespace. | ||
| 4. Quiesce Nexus Operations on the previous target Namespace. |
There was a problem hiding this comment.
Suggested change
| 4. Quiesce Nexus Operations on the previous target Namespace. | |
| 4. Prepare Nexus Operations on the previous target Namespace during the migration. |
| 4. Configure the Endpoint allowlist to allow calls from the original monolithic Namespace. | ||
| 5. New Nexus Operations will be routed from callers in the monolithic Namespace to the new Namespace. | ||
| 4. Quiesce Nexus Operations on the previous target Namespace. | ||
| 1. Leave the previous Worker deployment running until all existing Nexus Operations in the previous Namespace have completed (and their underlying Workflows, if any). |
There was a problem hiding this comment.
Suggested change
| 1. Leave the previous Worker deployment running until all existing Nexus Operations in the previous Namespace have completed (and their underlying Workflows, if any). | |
| 1. Leave the previous Worker deployment running until all existing Nexus Operations in the previous Namespace have completed. | |
| This includes their underlying Workflows, if they exist. |
| 5. New Nexus Operations will be routed from callers in the monolithic Namespace to the new Namespace. | ||
| 4. Quiesce Nexus Operations on the previous target Namespace. | ||
| 1. Leave the previous Worker deployment running until all existing Nexus Operations in the previous Namespace have completed (and their underlying Workflows, if any). | ||
| 2. Previous Workers in the monolithic Namespace can have the service implementation removed, since it is now being served from the new Endpoint target Namespace. |
There was a problem hiding this comment.
Suggested change
| 2. Previous Workers in the monolithic Namespace can have the service implementation removed, since it is now being served from the new Endpoint target Namespace. | |
| 2. Remove Workers from the monolithic Namespace, since those Workflows and Activities are now served from the new Endpoint targeted Namespace. |
| 2. If using Signal-with-Start behind a Nexus Operation, then a new entity-Workflow will be started in the new target Namespace. | ||
| 3. A cancel Nexus Operation request from a caller Workflow will be routed through the Nexus Endpoint to the new target Namespace, which may not have the underlying Workflow. | ||
|
|
||
| In these scenarios, Temporal can provide guidance on different migration strategies. |
There was a problem hiding this comment.
How should someone seek this guidance? Support? Community?
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.