You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking that maybe it would be useful, at least it would have been for some of my projects, to make the queue worker able to receive messages on plain json. This would allow third party services to send messages to be processed by laravel.
This would be very helpful in systems that need to integrate with legacy systems asynchronously.
For example, I have a central inventory systems that receive inventory movements and other data from an old branch POS soft.
We just need to have a predefined contract. In our case we just used a field "MessageType" that should be match with some configuration on the queue.php file to map it to a job. Here is an example:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I was thinking that maybe it would be useful, at least it would have been for some of my projects, to make the queue worker able to receive messages on plain json. This would allow third party services to send messages to be processed by laravel.
This would be very helpful in systems that need to integrate with legacy systems asynchronously.
For example, I have a central inventory systems that receive inventory movements and other data from an old branch POS soft.
We just need to have a predefined contract. In our case we just used a field "MessageType" that should be match with some configuration on the queue.php file to map it to a job. Here is an example:
on queue.php it could be mapped with something like this:
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions