PHPackages                             monadial/nexus-monorepo - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. monadial/nexus-monorepo

ActiveProject[Framework](/categories/framework)

monadial/nexus-monorepo
=======================

Nexus — A production-grade actor system for PHP 8.5+

v0.1.0(4w ago)10[5 PRs](https://github.com/nexus-actors/nexus/pulls)MITPHPPHP >=8.5.7CI passing

Since Feb 22Pushed 1w agoCompare

[ Source](https://github.com/nexus-actors/nexus)[ Packagist](https://packagist.org/packages/monadial/nexus-monorepo)[ RSS](/packages/monadial-nexus-monorepo/feed)WikiDiscussions main Synced 1w ago

READMEChangelog (1)Dependencies (40)Versions (89)Used By (0)

Nexus
=====

[](#nexus)

An actor system for PHP 8.5+. Type-safe actors, supervision trees, event sourcing, and multi-worker scaling — Akka and OTP patterns in the PHP you already know.

> **Maturity:** Nexus is a pre-1.0 actor-system toolkit under active development. APIs are subject to change, several subsystems are experimental, and the project is not yet production-hardened. Evaluate it accordingly before depending on it for critical workloads.

Why Nexus?
----------

[](#why-nexus)

PHP has mature tools for HTTP request handling, but nothing serious for building concurrent, long-running systems. When you need actors, supervision, or message-driven architectures, the answer has always been "use a different language." Nexus changes that.

**The problem.** Building concurrent PHP systems today means stitching together queue workers, process managers, and ad-hoc error recovery. There's no structured way to manage state across concurrent units, no supervision hierarchy to handle failures automatically, and no type safety for the messages flowing through your system.

**The approach.** Nexus brings battle-tested patterns from Akka and OTP to PHP with Psalm-assisted protocol checking. Every `ActorRef` is generic — with the optional Psalm plugin and concrete annotations enabled, message type mismatches are caught at analysis time. This is static analysis, not a runtime guarantee: at runtime boundaries (deserialization, dynamic dispatch) types are not enforced. Behaviors are immutable value objects. State is explicitly managed, never shared. The entire API is `readonly` and `final` by default.

**What makes it different:**

- **Two runtimes, one core API.** Write core actor code once. Run it on PHP Fibers during development and Swoole coroutines in production. Some features are runtime-specific — the worker pool and HTTP server are Swoole-only, and mailbox, shutdown, and cancellation semantics can differ between runtimes.
- **Supervision hierarchy.** Actors form a hierarchy. Parents supervise children. When something fails, the supervision strategy decides what happens. One-for-one restart directives with retry windows are implemented; all-for-one, escalation, and exponential-backoff strategies are currently incomplete.
- **PHP 8.5+ native.** Nexus uses `readonly class`, typed class constants, and generic templates throughout. Built for modern PHP, not retrofitted onto it.
- **PSR everywhere.** PSR-11 containers, PSR-3 logging, PSR-14 event dispatching, PSR-20 clocks. Nexus plugs into your existing stack.
- **Multi-worker scaling.** Scale actors across all CPU cores on a single machine via Swoole's `Thread\Pool`. Each worker runs an independent `ActorSystem`. `WorkerActorRef` delivers messages cross-thread via `Thread\Queue` — an indicative local microbenchmark measured ~260K msgs/sec per worker pair, but no published methodology exists yet and the committed performance suite is partially broken, so treat that figure as unverified. No application-level serializer is required (Swoole serializes internally).

Quick Example
-------------

[](#quick-example)

Two actors communicating with immutable messages using the Fiber runtime:

```