Laravel 5 Events and Queue

Question

As mentioned in Laravel docs (http://laravel.com/docs/5.1/events#defining-listeners), I can make a listener to be queued. This makes it possible to run events in an asynchronous manner.

I went more deep into this, and found out that I can even have the event to be fired in a separate Laravel installation, as long as they use the same queue instance(beanstalkd in my case) and they also share the same listener (the listener class should be defined in both installations).

Now I need some more information regarding this.

Is this OK? I mean, it works for now, but is it considered a "hack"? Is there any library or another way for this?
How can I have distributed events using this? I mean, when I fire an event somewhere, there will be some listeners that will be fired somewhere else. They are not on the same installation, and all of them has to be fired. This is not achievable with my current setup.

I think I'm looking for some distributed event system with Laravel, but I'm not sure...

Sangar82 · Accepted Answer · 2016-06-03 17:12:54Z

1

You don´t need a queue to achieve this. I had similar problem that you and I solve this at this way:

If you want to send events to your frontend on any machine I recommend you use Broadcasting events. You can use Redis or Pusher.
If you want to send events to your backend on any machine you need to use Redis Sub/Pub. You send a event from any place (PUBlisher) and you need in each machine a listener to get this event (SUBscribers).

I use too Beanstalkd to distribute jobs in several instances. Works like a charm!

answered Jun 3, 2016 at 17:12

Sangar82

5,2501 gold badge37 silver badges53 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Laravel 5 Events and Queue

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related