Independent deployment makes each workflow its own service, allowing teams to release, scale, and version it without coordinating with other workflows. The one-workflow-to-one-service boundary prevents shared deployment lifecycles and resource contention while preserving clear operational ownership. section 2.2.3 section 2.6
The boundary produces several operational effects:
- Release changes without coordinating with unrelated teams or workflows. section 2.2.3
- Scale each workflow according to its own traffic and metrics. section 2.2.3
- Run multiple versions simultaneously and shift traffic gradually. section 2.2.3
- Attribute observability data and costs to specific workflows without allocation logic for grouped services. section 2.2.3
- Accept the trade-off of managing more services as the platform grows. section 2.6
Patient assistant deployment
When Sarah defines a patient intake assistant with the @workflow decorator, it becomes a separate service with its own deployment lifecycle. She can update it without coordinating with another healthcare workflow, scale it on its own traffic, and run versions 1.0 and 2.0 concurrently. section 2.2.3

