2 posts tagged with "server"

Durable Workflow Server 3.0 is a native implementation of the standalone Server, written in Rust. It runs as a single process. You give it a database and a token. It creates its own schema, serves the API, and fires durable timers and schedules itself. You no longer deploy Redis, a queue worker, a scheduler or a bootstrap job alongside it.

Your workflows do not change. The native Server implements the same HTTP control plane and worker protocol, so existing PHP, Python and Rust workers connect to it as before.

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.