You’ve implemented multiple Cloud Functions to process order fulfillment. You must orchestrate function execution using each function’s output to decide flow, and you want minimal latency. What orchestrator and control flow should you use?

Workflows is the ideal choice for orchestrating Cloud Functions with minimal latency because it is a fully managed, serverless orchestration service designed for exactly this purpose. It allows you to define complex sequences of steps, including conditional logic (conditional jumps), retries, and parallel execution, directly within a workflow definition. This enables you to use the output of one function to determine the next step efficiently. Cloud Composer, while powerful for orchestrating complex data pipelines, introduces more overhead and latency due to its reliance on Apache Airflow and its underlying infrastructure. While it can call Cloud Functions, it's not optimized for the low-latency, event-driven orchestration described. Callbacks are a programming pattern, not a control flow mechanism within an orchestrator like Workflows, and would not be the primary way to define execution logic in this context.