Section 1

Workflows Product Playbook

Workflows

Product Baseline — standalone product knowledge block. This file contains the product knowledge needed to study this product independently.

Learning Map

By the end of this chapter, you should be able to reason about:

Purpose and workload fit
Core architecture and resource model
Key capabilities and operational model
Security and IAM
Networking / connectivity where relevant
Reliability, scaling and failure modes
Cost and performance considerations
Migration / integration patterns
Adjacent products and decision boundaries
Common anti-patterns and troubleshooting signals

Official Learning Resources

Section 2

Product Identity

Plain-language purpose: HTTP services orchestration.
Catalogue category: Integration services
Catalogue summary: HTTP services orchestration
Known aliases: Workflows

Need to Know

Workflows should be understood first by the workload problem it solves, not by memorizing its name. Use the learning map above as the chapter checklist and deepen each area as verified product research is added.

When to Choose

Choose Workflows when its architectural layer, workload model, operational ownership, and hard constraints align with the requirement. Do not select it merely because it appears in an answer option or shares a feature with another service.

Architecture & Resource Model

Document the canonical components, control plane/data plane boundaries, and service handoffs here. Prefer a Mermaid sequence diagram when data or requests move through several services.

Core Capabilities

Capture the capabilities that materially affect architecture: scaling model, state model, protocols, data semantics, deployment unit, and managed-vs-self-managed responsibilities.

Security & Networking

Capture IAM, identity, encryption/key control, ingress/egress, private connectivity, and perimeter implications that are specific to this product.

Reliability & Scaling

Explain the failure domains the product protects against, what remains the customer’s responsibility, scaling boundaries, and any RTO/RPO implications.

Performance & Cost

Teach the cost drivers and performance levers together. Prefer root-cause reasoning over generic “add capacity” guidance.

Runtime / Framework Compatibility

Record language, framework, protocol, or ecosystem compatibility only where it materially changes product selection. Version-sensitive facts should be verified against current official documentation.

Migration / Modernization

Separate compatibility-preserving migration from architectural modernization. A low-risk migration target and the long-term cloud-native target can be different.

Adjacent Products / Decision Boundaries

Compare Workflows with the products most likely to be confused with it. Use “choose X when…” statements rather than feature inventories.

Common Anti-Patterns

Record wrong-layer solutions, unnecessary self-management, incompatible protocols/access patterns, and operational designs that merely mask the root problem.

Section 3

Terminology for Reasoning

Start with the product’s own vocabulary. The third column turns each term into a reasoning cue rather than a definition to memorize.

Product term	Meaning	Why it matters when reasoning
Workflow	Deployed YAML/JSON definition describing ordered service calls and control flow.	Best fit for service orchestration where state/control flow matters more than data-plane processing.
Step	Named unit in a workflow definition.	Makes retries, branching, assignments, and calls explicit in the orchestration graph.
Execution	One run of a deployed workflow.	Separate the durable workflow definition from an individual invocation and its state.
Connector	Built-in integration simplifying calls to supported Google Cloud APIs.	Reduces HTTP/authentication boilerplate for service orchestration.
Callback	Mechanism that lets an execution wait for an external event/request.	Useful for long-running human/system interactions without polling loops.
Retry policy	Rules controlling retry of failed calls.	Reason about idempotency before enabling retries; orchestration retries can repeat side effects.

Cross-product reasoning vocabulary

Reasoning term	Meaning
Purpose	The primary problem the product exists to solve.
Workload shape	The characteristic form of the work, such as batch, streaming, transactional, analytical, orchestration, messaging, or storage.
Architectural layer	Where the product acts in the system, such as ingestion, transport, processing, storage, serving, orchestration, governance, security, or operations.
Operational model	What Google manages and what the customer still configures, secures, monitors, and operates.
Decision boundary	The requirement that makes this product a better or worse fit than an adjacent product.
Anti-pattern	A requirement or design choice that conflicts with the product’s purpose or operating model.

Use the product terms first, then use the cross-product vocabulary to explain why those concepts change an architectural decision.

Section 4

Knowledge Check

Question	Resolution guidance
What primary workload is Workflows designed to solve?	Resolve: Workflows is primarily for http services orchestration. Then classify that purpose by workload shape and architectural layer, and explain why that makes the service a fit. Do not stop at a feature list.
When is Workflows the wrong choice?	Use the anti-patterns and decision boundaries. Name cases where another product better matches the workload, access pattern, compatibility, failure domain, or operational-control requirement.
What adjacent products are most easily confused with it?	State the decisive boundary as: Choose X when …; choose Y when …. Prefer workload and constraint reasoning over feature lists.
What operational responsibilities remain with the customer?	Separate what Google manages from what the customer must still design, configure, secure, monitor, test, or operate.
What reliability, security, performance, and cost factors matter most?	Explain the important failure boundaries, controls, performance levers, and cost drivers, including why each design choice changes the outcome.
How would you recognize Workflows without seeing the product name?	Recognize the workload, hard constraints, architectural layer, compatibility requirements, and operational model—the problem signature that points toward Workflows.

Section 5

Conclusion

Start with the workload: understand the problem Workflows is designed to solve before memorizing features.
Use constraints to decide: access pattern, compatibility, failure domain, operational ownership, security, performance, and cost should drive the choice.
Know the boundaries: explain when an adjacent product is a better fit and why.
Reason about operations: distinguish managed capabilities from customer responsibilities.
Recognize the problem signature: identify Workflows from architectural requirements even when its name is absent.
Revisit weak areas: use the Learning Map and Knowledge Check to decide what to review next.

Section 6

Maintenance Notes

Prefer durable product facts and product-level decision boundaries. Verify volatile runtime, version, quota, pricing, and availability details against official product documentation before updating this material.