Which HTTP stack should serve Durable Workflow Server? We measured Apache, PHP-FPM, and persistent PHP workers against the same application workload. The answer depends on the whole request path, including the time SDK workers spend waiting for tasks. Here are the results, what they mean for our Server, and why a different application might choose differently.
Today we are announcing Durable Workflow 2.0, the evolution of the PHP-native project formerly known as Laravel Workflow into a standalone, polyglot durable execution platform.
Modern systems rarely live in one language or one process. PHP may own the application, Python the data and AI workloads, and Rust the performance-critical services. Durable Workflow 2.0 gives those systems one durable execution model, one protocol, and one operational surface. It is built for software developed and operated by people and, increasingly, by autonomous agents.