When
building Durable
Functions apps, it’s inevitable that orchestrations need to be changed. You
might need to modify or remove activity functions, or maybe even completely
rewrite the orchestration logic. Without any functionality built around
versioning, it’s difficult to introduce changes to orchestrations, especially
when they’re in-flight.
The
orchestration versioning feature allows you to set the version of orchestrations
so that you can write conditional logic to control when a certain orchestration
version is run. Furthermore, the feature allows you to version workers,
so that orchestrations of a certain version can only be run on certain workers.
This is useful when you need to make big or breaking changes to your
orchestrations and want to have both new and existing inflight orchestrations
run concurrently.
The
orchestration versioning feature is now available for .NET isolated Durable
Function apps using any of the supported storage providers, including the
latest durable
task scheduler.
In addition
to Durable Functions, the durable task
SDK for .NET also supports the orchestration versioning feature. This is a
lightweight client SDK for users that don’t want to use Durable Functions to
author orchestrations and are looking to run their apps outside of Azure
Functions.
Learn more.