A high-performance PHP application server and process manager written in Go, designed to replace traditional Nginx+FPM setups.
RoadRunner is a high-performance PHP application server and process manager written in Go. It replaces traditional Nginx+FPM setups by running PHP applications as persistent services, significantly improving throughput and resource efficiency. Its plugin-based architecture extends functionality with features like HTTP/2/3 servers, queue drivers, gRPC, and workflow orchestration.
PHP developers and DevOps engineers building scalable, high-performance web applications and microservices who need a modern alternative to traditional PHP-FPM setups.
Developers choose RoadRunner for its exceptional performance, extensibility via plugins, and production-ready features like automatic TLS, metrics, and workflow support—all while maintaining compatibility with PSR standards and existing PHP codebases.
🤯 High-performance PHP application server, process manager written in Go and powered with plugins
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Written in Go, RoadRunner manages PHP processes persistently, reducing per-request overhead and significantly boosting throughput compared to traditional Nginx+FPM, as emphasized in its value proposition.
Its plugin-driven architecture supports diverse functionality like HTTP/2/3 servers, queue drivers (RabbitMQ, Kafka), KV stores (Redis, Memcached), and gRPC, allowing customization per project needs.
Offers PSR-7/17-compatible HTTP servers with automatic TLS management, 103 Early Hints, and middleware (gzip, prometheus), ensuring up-to-date web capabilities directly from the README.
Includes built-in observability with OpenTelemetry, a metrics server, and systemd-like service management with auto-restarts, making it reliable for deployments as highlighted in features.
Requires managing Go binaries, specific PHP extensions (php-sockets, php-curl), and YAML configuration, which is more involved than standard PHP-FPM setups, as noted in installation warnings.
Adopting RoadRunner ties your stack to its plugin ecosystem; if plugins become unmaintained or lack features, it can limit flexibility compared to more standardized solutions.
Developers must understand both PHP worker models and RoadRunner's configuration, adding complexity for teams familiar only with traditional web servers like Apache or Nginx.