reactphp.org

What It Is

ReactPHP is an event-driven, non-blocking I/O component ecosystem for PHP. Based on the reactor pattern, it is aimed at high-performance network servers and clients, long-running applications, and scenarios that require cooperative multitasking. The source material emphasizes that it is production-ready, battle-tested, and has millions of installations.

Core Capabilities

In terms of functionality, ReactPHP is not just a single event loop library, but a set of composable components: EventLoop handles the event loop, Stream provides non-blocking readable and writable streams, Promise/Async manages asynchronous control flow, Socket supports TCP/TLS, Datagram supports UDP, HTTP provides streaming clients and servers, DNS offers asynchronous resolution, and there are also utility components such as Cache, ChildProcess, and PromiseTimer. It is non-blocking by default, and worker processes are recommended when dealing with blocking I/O.

Language, Ecosystem, and Documentation

ReactPHP primarily serves PHP developers. It supports PHP 8+ and PHP 7+, while retaining compatibility with PHP 5.3+ and HHVM. It runs cross-platform without requiring extensions, and can achieve better performance when optional extensions are available. On the ecosystem side, the source text mentions hundreds of third-party libraries that can connect to network services, databases, and third-party APIs, and lists projects such as Ratchet, Predis Async, Thruway, and PHP-PM. Documentation is provided by component, with additional resources including articles, talks, Gitter, issues, and Twitter channels. Overall, the documentation coverage is fairly strong.

Pricing and Support

No commercial pricing is mentioned in the source text. The project is closer to a free and open-source library model, with maintainers able to receive sponsorship through GitHub Sponsors. Support mainly comes from public issues, the Gitter community, Twitter updates, and core team email. The upside is open communication and reusable community knowledge; the limitation is that the core team is small and primarily volunteer-based, so it should not be expected to provide a commercial SLA.

Pros, Cons, and Who It’s For

Its strengths are maturity, stability, decoupled components, broad compatibility, and a rich ecosystem. It is suitable for PHP teams building WebSocket services, asynchronous HTTP, TCP/TLS/UDP services, async Redis clients, long-running processes, and similar systems. The downside is that the asynchronous programming model has a learning curve for developers used to traditional PHP request-response workflows, and some older components are deprecated or legacy, so newer components should be selected where appropriate.

Access from China

The source text does not provide information about mainland China network access, mirrors, or payment options, so access conditions are rated as unknown. For teams deploying in China, it may be worth evaluating PHP asynchronous solutions such as Swoole, Workerman, and Amp as well. If cross-language options are acceptable, event-driven ecosystems such as Node.js and Twisted can also be compared.