# Child Workflows - Temporal feature

> Leverage Temporal Child Workflows for enhanced composability and efficiency. Partition steps, manage resources, invoke multiple services, and execute periodic logic seamlessly.

In Temporal, **Child Workflows** enable applications to achieve another level of composability when it comes to throughput.

The following example scenarios are a few reasons to use this feature:

- To create a separate service that can be invoked from multiple other services or applications.
- To partition a step into smaller chunks.
- To manage a dedicated resource and guarantee uniqueness.
- To execute logic periodically without overwhelming the parent business process.

See the SDK feature guides for implementation details:

**Related:**

- [Go SDK Child Workflow feature guide](/develop/go/workflows/child-workflows)
- [Java SDK Child Workflow feature guide](/develop/java/workflows/child-workflows)
- [PHP SDK Child Workflow feature guide](/develop/php/workflows/child-workflows)
- [Python SDK Child Workflow feature guide](/develop/python/workflows/child-workflows)
- [TypeScript SDK Child Workflow feature guide](/develop/typescript/workflows/child-workflows)
- [.NET SDK Child Workflow feature guide](/develop/dotnet/workflows/child-workflows)
- [Ruby SDK Child Workflow feature guide](/develop/ruby/workflows/child-workflows)
- [Rust SDK Child Workflow feature guide](/develop/rust/workflows/child-workflows)

For a deep dive into Child Workflows see the [Child Workflows Encyclopedia page](/child-workflows).