Download the PHP package netlogix/jobqueue-scheduled without Composer
On this page you can find all versions of the php package netlogix/jobqueue-scheduled. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download netlogix/jobqueue-scheduled
More information about netlogix/jobqueue-scheduled
Files in netlogix/jobqueue-scheduled
Package jobqueue-scheduled
Short Description Allows for scheduled jobs and deduplicates
License MIT
Informations about the package jobqueue-scheduled
Netlogix.JobQueue.Scheduled
This package provides a PDO based scheduler for JobQueue jobs.
There are two main goals:
- Schedule a Flowpack JobQueue job for later execution.
- Have a single job only scheduled once.
Installation
Schedule jobs
The first goal of this package is to have a way to put any kind of JobQueue job on hold and mark it for later execution. In contrast to e.g. "Defer" annotated methods or default behavior of JobQueue jobs, there is a time aspect to it. Scheduled jobs are not executed immediately but at a time specified while scheduling.
Regular job queue jobs need to be serializable. That's just an implementation detail of how Flowpack FakeQueue and t3n RabbitQueue work.
To schedule an existing Flowpack job, just wrap it in a Scheduled Job and pass it to the scheduler.
Jobs with unique identifiers
The second goal of this package is to avoid duplicate schedules.
Certain jobs don't calculate a specific computation but just "run to the end". An example of those are the catchup jobs of the Neos.EventSourcing package. Queuing triggers the catchup call of some event listeners.
Queuing another catchup job while the first one is running is good because there might be additonal changes.
Queueing another catchup job while the previous one has is not even started is unnecessary because the first one will already catch up to the end.
The "schedule" will only schedule a new job if the specified identifier is not already scheduled. If there are conflicts between the existing due date and the one provided by the new job the earliest value is taken.
Queue scheduled jobs
A scheduled job lives in the database and is not processed any further until queueing happens.
This is currently done via cronjobs.
The internal scheduling mechanism will make sure only those jobs are passed from the scheduler to the job queue which are "due" according to their individual due date values.
Automatically schedule jobs
Some jobs originate from foreign applications. An example would be one flow app putting a job into a RabbitMQ and another flow app consuming it.
Previously the only implementation would be a regular jobqueue worker, which neither provides a way to delay execution nor a deduplication feature.
Now every job can simply implement the ScheduledJobInterface
. When execute()
is triggered, it's now moved over to a scheduled jobs queue.
The job itself must provide all necessary details about how to schedule its execution.
All versions of jobqueue-scheduled with dependencies
doctrine/orm Version ^2.6
flowpack/jobqueue-common Version ^3.0
neos/flow Version ~8.3
php Version ~8.2 || ~8.3