Closed di-sysops closed 9 years ago
Hello all,
For those who have this issue, the following ZF2 module is designed to solve this problem as a whole.
I anticipate marking it as stable after some additional testing in a real environment.
https://packagist.org/packages/jackdpeterson/immutable-state-status-tracker
Thanks!
Hello fellow developers, this is not an issue per-se with the SlmQueue module specifically, but rather, a question about how one ought to report on the state of a given workflow.
For the sake of this discussion, let's assume we have just a single default queue.
We have a workflow consisting of the following three steps (based on the examples used in this module's documentation)
I can see a number of ways that one could report on the status of where a workflow is at in processing; however, I would appreciate some second and third opinions on how to approach reporting on the state of a workflow that leverages SlmQueue. Pros/Cons are also appreciated (e.g., dealing with data collisions etc.).
Possibility 1: --> each job inserts or updates an array into an object cache like redis and assembled into something like:
Any and all thoughts are appreciated here! I'm assuming that this is a question that just about any developer has to deal with when it comes to pushing tasks to background processing when dealing with client-facing applications.
Thanks!