Can Cloud Workflows be used for orchestration AND transformation?

[jfbaro]

Hi there,

I hope you guys are doing well.

We are evaluating some solutions (Apache Camel K and the likes) to allow teams to:

• Low Code protocol transformation (Kafka, FTP, S3, MQ, SOAP, SFTP, gRPC, GraphQL, etc.) One team in particular has to integrate their product with 100s of external partners (each one uses a different integration technology), and writing each integration "by hand" would be a waste of time/motivation.
• Enrich integrations' payloads (by calling both internal and external services)
• Pay per execution/transformation/step (SERVERLESS)
• Orchestrate processes that span multiples domain/services (On either our GCP account or Partners external Datacenters)
• Strong retry and monitoring capabilities
• Be part of our CI/CD pipeline (and not be limited to a Graphical interface)

The items in bold seem to be part of what Cloud Workflows does natively, but are the other requirements something that can be added to (or achieved with) GCW and keep "serverless"? Please.

Any help would be appreciated.

Thanks

[atamel]

Workflows is not for transforming data directly but it can have a transformation step where it can call another Cloud Function or Cloud Run service to transform the data. Everything is still serverless in this model (serverless orchestration with Workflows and serverless transformation with Cloud Function/Run).