Skip to content

Commit 44af64c

Browse files
committed
Remove "Overview" heading
1 parent 9fb169e commit 44af64c

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

articles/azure-functions/durable/durable-functions-orchestration-versioning.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,29 +11,27 @@ ms.custom: fasttrack-edit
1111

1212
# Orchestration versioning in Durable Functions (Azure Functions)
1313

14-
## Overview
15-
1614
Orchestration versioning addresses [the core challenge](durable-functions-versioning.md) of deploying changes to orchestrator functions while maintaining the deterministic execution model that Durable Functions requires. Without this feature, breaking changes to orchestrator logic or activity function signatures would cause in-flight orchestration instances to fail during replay because they would break the [determinism requirement](durable-functions-code-constraints.md) that ensures reliable orchestration execution.
1715

1816
Sub-orchestrations can also leverage this feature.
1917

20-
### Terminology
18+
## Terminology
2119

2220
This article uses two related but distinct terms:
2321
- **Orchestrator function** (or simply "orchestrator"): Refers to the function code that defines the workflow logic - the template or blueprint for how a workflow should execute.
2422
- **Orchestration instance** (or simply "orchestration"): Refers to a specific running execution of an orchestrator function, with its own state, instance ID, and inputs. Multiple orchestration instances can run concurrently from the same orchestrator function.
2523

2624
Understanding this distinction is crucial for orchestration versioning, where the orchestrator function code contains version-aware logic, while orchestration instances are permanently associated with a specific version when created.
2725

28-
### Key benefits
26+
## Key benefits
2927

3028
- **Zero-downtime deployments**: Deploy breaking changes without waiting for in-flight orchestrations to complete.
3129
- **Rolling upgrades**: Workers running different versions of orchestrator code can coexist safely.
3230
- **Automatic version isolation**: The runtime ensures version compatibility automatically.
3331
- **Minimal configuration**: Built-in feature requiring only basic `host.json` configuration.
3432
- **Backend agnostic**: Feature can be used by apps leveraging any of the Durable Function's [storage backends](durable-functions-storage-providers.md).
3533

36-
### How it works
34+
## How it works
3735

3836
The orchestration versioning feature operates on these core principles:
3937

0 commit comments

Comments
 (0)