## Metadata - Author: [[hubert-dulay|Hubert Dulay]] - Full Title:: Limits of the Event-Driven Orchestrator - Category:: #🗞️Articles - Document Tags:: [[Workflow orchestrators|Workflow Orchestrators]] [[Workflow orchestrators|Workflow Orchestrators]] - URL:: https://stkbailey.substack.com/p/limits-of-the-event-driven-orchestrator#%C2%A7streaming-workflow-builders - Finished date:: [[2023-04-10]] ## Highlights Referenced from [[Life after orchestrators|Life After Orchestrators]]. It is a bit weird: who wanted to do streaming processing with an orchestrator? > This is essay #5 in the Symposium on [Is the Orchestrator Dead or Alive](https://stkbailey.substack.com/p/symposium-invitation-is-the-orchestrator)? ([View Highlight](https://read.readwise.io/read/01gxnfmw4ddkfspy6dvd2w0bsq)) > Airflow and Dagster are similar to CRON with additional enhancements ([View Highlight](https://read.readwise.io/read/01gxngzbd20veaqq89wmahm73p)) > With this understanding of orchestrators, I’ll try to use another event-driven orchestrator called Prefect. ([View Highlight](https://read.readwise.io/read/01gxngzjhpcf2c7sg6n5hy1r6w)) > [Prefect](https://www.prefect.io/opensource/) is an open-source orchestration platform that looks promising. It natively has a way to consume events ([View Highlight](https://read.readwise.io/read/01gxnh0cvke2t4w1q5170rz261)) > orchestrators cannot replace today’s popular stream processors ([View Highlight](https://read.readwise.io/read/01gxnh1pbg2672vh9arr78zc80)) > what is event-driven orchestration supposed to do? The answer is really notifications. Event-driven orchestrations are really notification consumers. They only trigger tasks and do not define the task itself. The tasks that orchestrators invoke could be a batch process that can handle large volumes of data but that data wouldn’t come from Kafka. Batch data comes from data stores that hold data at rest. ([View Highlight](https://read.readwise.io/read/01gxnh26w9as7bzzbmb2pn4h0n))