> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/release-orchestration/new-to-release-orchestration/use-cases.md).

# Applications

This topic outlines common scenarios where Release Orchestration helps teams model, schedule, and execute releases with clear visibility.

### Micro Service Releases <a href="#micro-service-releases" id="micro-service-releases"></a>

#### Challenge <a href="#challenge" id="challenge"></a>

Coordinating releases across multiple microservices that have dependencies on each other, requiring careful sequencing and coordination.

#### Solution <a href="#solution" id="solution"></a>

Use a single process with phases, activities, and dependencies to coordinate the release across services.

#### Example <a href="#example" id="example"></a>

A banking application requires coordinated releases of:

* Payment service
* Account service
* Notification service
* API gateway

Model the release as one process, add pipeline activities for each service deployment, and use dependencies to control order.

![Harness AI generating a coordinated release process for a banking application, with phases for each service deployment and owner assignments](/files/0uxarQwo4T5OkNudZ2qe)

### Scheduled Releases <a href="#scheduled-releases" id="scheduled-releases"></a>

#### Challenge <a href="#challenge" id="challenge"></a>

Managing recurring releases on a regular cadence (weekly, monthly, quarterly) with consistent processes.

#### Solution <a href="#solution" id="solution"></a>

Use **release groups** and the **Release Calendar** to model business cadence (for example, weekly releases).

#### Example <a href="#example" id="example"></a>

A SaaS product releases new features every two weeks. Create a release group with a recurring cadence, link it to the process, and open a release from the calendar to pre-execute it and provide inputs.

![Harness AI generating a bi-weekly SaaS feature release process with four sequential phases: Planning, Development, Testing, and Deployment](/files/FCuWy7U6aKgvKSHwpY8S)

### Compliance and Audit Requirements <a href="#compliance-and-audit-requirements" id="compliance-and-audit-requirements"></a>

#### Challenge <a href="#challenge" id="challenge"></a>

Meeting regulatory requirements for financial services, healthcare, or other regulated industries that require detailed audit trails and compliance controls.

#### Solution <a href="#solution" id="solution"></a>

Capture approvals/sign-offs using manual activities and use traceability to link what was executed in a release.

#### Example <a href="#example" id="example"></a>

A healthcare application must demonstrate:

* Who approved each release
* When approvals were given
* What changes were included
* Rollback procedures documented

Model a QA sign-off as a manual activity, record sign-off inputs during execution, and use the release execution history as audit evidence.

### Cross-Team Coordination <a href="#cross-team-coordination" id="cross-team-coordination"></a>

#### Challenge <a href="#challenge" id="challenge"></a>

Coordinating releases that involve multiple teams (development, QA, operations, security) with different schedules and priorities.

#### Solution <a href="#solution" id="solution"></a>

Assign owners to phases and activities and use notifications to bring the right owners in when input is required.

#### Example <a href="#example" id="example"></a>

A release requires:

* Development team: Code changes
* QA team: Testing and validation
* Security team: Security review
* Operations team: Deployment

Model each group of work as a phase, assign owners, and rely on “on hold / input required” notifications when manual input or sign-off is needed.

### Complex Deployment Pipelines <a href="#complex-deployment-pipelines" id="complex-deployment-pipelines"></a>

#### Challenge <a href="#challenge" id="challenge"></a>

Managing releases that involve multiple environments, complex validation steps, and conditional logic.

#### Solution <a href="#solution" id="solution"></a>

Use phase and activity dependencies to model parallel and sequential execution across phases and environments.

#### Example <a href="#example" id="example"></a>

A release process includes:

* Development environment
* Integration testing
* Staging environment
* User acceptance testing
* Production deployment
* Post-production validation

Model each stage as a phase and connect them with dependencies (for example, UAT depends on Staging, Production depends on UAT).

### Emergency Releases <a href="#emergency-releases" id="emergency-releases"></a>

#### Challenge <a href="#challenge" id="challenge"></a>

Managing urgent releases (hotfixes, security patches) that need to bypass normal processes while maintaining control and documentation.

#### Solution <a href="#solution" id="solution"></a>

Use a dedicated process for emergency workflows (for example, fewer phases with explicit manual sign-off).

#### Example <a href="#example" id="example"></a>

A critical security vulnerability requires:

* Immediate assessment
* Fast-track approval
* Emergency deployment
* Post-deployment validation
* Documentation for audit

### Release Rollback <a href="#release-rollback" id="release-rollback"></a>

#### Challenge <a href="#challenge" id="challenge"></a>

Managing rollback scenarios when releases fail or cause issues, requiring coordinated reversal across multiple systems.

#### Solution <a href="#solution" id="solution"></a>

Model rollback as phases and activities in your release process so it’s executed consistently when needed.

#### Example <a href="#example" id="example"></a>

A production release causes issues:

* Automatic rollback trigger
* Coordinated rollback across services
* Validation of rollback success
* Root cause analysis

### Release Metrics and Reporting <a href="#release-metrics-and-reporting" id="release-metrics-and-reporting"></a>

#### Challenge <a href="#challenge" id="challenge"></a>

Tracking release metrics, success rates, and performance across multiple releases to identify improvement opportunities.

#### Solution <a href="#solution" id="solution"></a>

Use the release execution history and traceability data to understand what ran and how releases performed over time.

#### Example <a href="#example" id="example"></a>

Organizations need to track:

* Release frequency
* Success rates
* Time to production
* Rollback frequency
* Approval cycle times

### Real-World Use Cases <a href="#real-world-use-cases" id="real-world-use-cases"></a>

#### Coordinated Multi-Service Releases <a href="#coordinated-multi-service-releases" id="coordinated-multi-service-releases"></a>

Orchestrate releases involving multiple microservices, enabling upstream dependencies, each with its own pipeline, ensuring all are deployed in the correct order with required approvals.

#### Feature Flag Rollouts <a href="#feature-flag-rollouts" id="feature-flag-rollouts"></a>

Model the process from feature development to gradual enablement and GA, tracking every step and approval.

#### Wave Deployments <a href="#wave-deployments" id="wave-deployments"></a>

Release to risk-taking customers first, then to the broader user base, with full traceability and rollback support.

#### Centralized Release Calendar <a href="#centralized-release-calendar" id="centralized-release-calendar"></a>

Track all in-flight and completed releases, with drill-down into phases and activities.

#### Incident Response and Rollback <a href="#incident-response-and-rollback" id="incident-response-and-rollback"></a>

Instantly identify which commits, artifacts, and tests are in a deployment, enabling rapid rollback and root cause analysis.

#### Managing the Entire Lifecycle of Software Delivery <a href="#managing-the-entire-lifecycle-of-software-delivery" id="managing-the-entire-lifecycle-of-software-delivery"></a>

Plan the release starting from infrastructure provisioning, building the artifact for the release, validating the build, running security functions, and deploying to production in waves.

### Related Topics <a href="#related-topics" id="related-topics"></a>

* [What is Release Orchestration](/release-orchestration/new-to-release-orchestration/getting-started.md)
* [Key Concepts](/release-orchestration/new-to-release-orchestration/key-concepts.md)
* [Multi-Service Release Example](/release-orchestration/troubleshooting-and-resources/release-orchestration-use-cases/multi-service-release-example.md)