Thanks for your question and happy you appreciate that content.

Cloud Composer is an orchestrator. Cloud Workflows is an orchestrator. Therefore, they both solve the same thing.

I personally prefer Cloud Workflows: it's serverless (cost effective) and it orchestrate only. With composer, the limits of processing, orchestration, scheduling and alerting are very blurry and can lead to bad practices/bad patterns.

Anyway, Airflow has great feature, like backfill and retry a pipeline at the step of the error (for now impossible with Cloud Workflows).

But I won't choose a tool, for a 1 time process (backfill, get history of something), and for error handling (I prefer the utopia of no error world and bet on that happy path!).

So, Cloud Workflows wins!! ;)

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

guillaume blaquiere
guillaume blaquiere

Written by guillaume blaquiere

GDE cloud platform, Group Data Architect @Carrefour, speaker, writer and polyglot developer, Google Cloud platform 3x certified, serverless addict and Go fan.

No responses yet

Write a response