I spent some time re-building the abstractions for background tasks in PHPNomad, but this time it’s through the lens of a Redis integration.

Summary The phpnomad/tasks package has been rewritten in v2.0.0 to introduce a modern, dependency-injection-friendly, platform-agnostic task system. This update deprecates the legacy TaskScheduler and CanScheduleTasks model and replaces it with a new, unified architecture centered around: This issue proposes refactoring the WordPress integration to fully adopt the new task system. Why The current WordPress integration schedules tasks using TaskScheduler, which is tightly coupled to the now-deprecated CanScheduleTasks API. That implementation is: Bringing the WordPress integration in line with the new task model will simplify the codebase, improve maintainability, and ensure consistency across all platform integrations. What Needs to Happen Compatibility…

The current datastore interface returns arrays for collection methods which leads to memory and performance issues in REST implementations where N+1 queries are sometimes unavoidable. By changing these methods to use generators, we can process items as they arrive and maintain constant memory usage regardless of collection size, creating a more efficient implementation without sacrificing usability.

We’re moving datastore events out of the database layer and into the datastore layer while also splitting operation traits into paired versions (with and without events) to give developers more control over event emission. This change breaks backward compatibility but creates a more flexible, truly nomadic system where developers can choose exactly which operations should emit events rather than being forced into a one-size-fits-all approach.

I have come to realize it’s likely time to pivot away from PHPNomad’s simple container system, and embrace integrating with existing solutions, instead.