Skip to content

Conversation

@Bueller87
Copy link
Contributor

What changed:

Added blog with examples for Batch Future
Added myself to the authors.yml

Copy link
Member

@shijiesheng shijiesheng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great writing!

Check out our [Batch Future sample](https://github.com/cadence-workflow/cadence-samples/tree/master/cmd/samples/batch) to see it in action.

### 3. Migrate Your Workflows
Identify workflows that process multiple items and convert them to use Batch Future:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's actually not that easy to migrate. Users need to have version control for backward compatibility. This is almost always the case when workflow logic has changed. See https://cadenceworkflow.io/docs/go-client/workflow-versioning#versioning

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-wrote the Migrate Your Workflows section. Take a look!

@Bueller87 Bueller87 force-pushed the add-batch-future-blog branch from 39d3a9b to 369ea6a Compare September 30, 2025 18:54
Signed-off-by: “Kevin” <[email protected]>
@Bueller87 Bueller87 merged commit ae015cc into cadence-workflow:master Sep 30, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants