Workflow

Automate and manage complex processes, financial transactions, data pipelines, microservices, job tracking, user signup flows and more!

[Workflow @DurableWorkflow]

Waterline for workflows. Horizon for queues.

[Laravel News @laravelnews]

Laravel Waterline: UI for Workflows https://t.co/bjdQKHPCi8 posted by @paulredmond

[Taylor Otwell @taylorotwell]

𝚞𝚜𝚎 𝚕𝚊𝚛𝚊𝚟𝚎𝚕::{𝙰𝚙𝚙𝚕𝚒𝚌𝚊𝚝𝚒𝚘𝚗, 𝚒𝚗𝚎𝚛𝚝𝚒𝚊};

𝚞𝚜𝚎 𝚌𝚛𝚊𝚝𝚎::𝚑𝚝𝚝𝚙::𝚖𝚒𝚍𝚍𝚕𝚎𝚠𝚊𝚛𝚎::𝙷𝚊𝚗𝚍𝚕𝚎𝙸𝚗𝚎𝚛𝚝𝚒𝚊𝚁𝚎𝚚𝚞𝚎𝚜𝚝𝚜;
𝚞𝚜𝚎 𝚌𝚛𝚊𝚝𝚎::𝚛𝚘𝚞𝚝𝚎𝚜;

[Workflow @DurableWorkflow]

@JackEllis We did something similar. Memory should probably also be considered.

[Workflow @DurableWorkflow]

https://t.co/WbFG5WyrRR

[Workflow @DurableWorkflow]

https://t.co/WbFG5WyrRR

[Workflow @DurableWorkflow]

That doesn’t diminish what has changed. It tells us what changed: we’ve experienced an enormous reduction in the marginal cost of attempted cognition, not the abolition of scarcity, causality, dependency, verification, or time.

[Workflow @DurableWorkflow]

Tokens are becoming cheap enough that we should stop optimizing intellectual work as though every additional attempt were expensive.

[DHH @dhh]

That means that rewriting ttfx in assembler doesn't mean I can't also do everything else I set my mind to. Because it doesn't cost any meaningful amount of attention or time. It's just tokens! That's why we can fix everything!

[Workflow @DurableWorkflow]

The fact that any bugs still exist at all is evidence that this just isn’t the case.

[Workflow @DurableWorkflow]

Will post the full results once the comparison has finished! Stay tuned!

[Workflow @DurableWorkflow]

I asked the agents a simple question: which stack serves our workflows fastest? The answer was surprising, not because we unseated our default Apache+mod_php, but because it exposed bugs that would make things slow no matter what stack we used.

[Workflow @DurableWorkflow]

So the runtime question is still open. But the real ROI so far wasn't "pick a faster server", it was using the hunt as an exercise to stress the system hard enough that it told us what was actually broken.

[Workflow @DurableWorkflow]

Between the old and new package names, Durable Workflow has passed 1M composer installs and now sees about 150K more every month. Thank you to everyone building with it. You’re awesome! 🙌

[Workflow @DurableWorkflow]

Pick the runtime capacity you need. Pay a predictable monthly price. Retries, timers, signals, queries, child workflows, and activity attempts don’t become surprise line items.

We publish the benchmark for every tier so you can see what that capacity actually delivers.