Eloquent Observers or Events Listeners? Which is Better? 

A bit late, but if someone runs into same issue there are 2 options withoutEvents or saveQuietly on the model

@@sadgshb ooh. So there's save quietly option. Thanks.

Services allows you to move the logic outside of controller, so that the logic code is more reusable, whereas events provide more control of *when* the logic should be dispatched. Event is also queueable, meaning it can perform long tasks or jobs in background. Event allows you to define new lifecycle of an action. For example you might want to execute background task of creating a information archive of user activity when user asks for it. The process may take about 1-2 days. Then the archive is added to storage for 30 days. After that you want to send a notification to user via email, informing them that the backup is successfully created. The problem with event is that if your event handles something that *transforms* the data, its result will be hard to debug because event doesn't explicitly throws exception in production environment if it fails to handle the data. The event's logics are invisible because of code decoupling through listeners. A single event may have multiple listeners. If the job fails, the event will simply throws exception to failed jobs and the tasks will move on. Which is why it's hard to read and follow. (please correct me about that last part because I'm not really sure myself)

Yes, observers: github.com/LaravelDaily/laravel-tips#set-logged-in-user-with-observers Also, video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-nCiNqboYFVQ.html

Boot method is good in this case. Because the logic is not that big and it is related to model and it should remain in the model.

@@AtiqSamtia boot method is in model?

It's very personal and depends on your server setup and how familiar you are with those tools. Personally, our team use Redis and Laravel Horizon, mostly.

For that, you would queue the events with retry parameter and error logging. Can't answer all of that in one comment, sorry, maybe at some point I should shoot a video, but it depends very much on your server setup and queue configuration is more about server config than Laravel code.

Pakistan 🇵🇰 2

Use jobs to handle your notifications

And make sure you have a failed jobs table

Taghwo Millionaire O. BTW failed jobs table comes by default with laravel7. And aahh, here i must setup a supervisor that sucks for local environment specially Windows.

Just implement ShouldQueue interface in your event listener class

Sorry, maybe I didn't emphasize it right. In this case, both observer and listener use THE SAME notification class to send. It's just a different way to call that notification.

Use queue

I don't use any plugins, search my channel for phpstorm, I have a few videos with tips

Hi, no idea, to be honest, never tried anything like that.

@@PovilasKorop Thanks for your reply that quick. (for other viewers, if anyone has the solution please suggest and help will be much appreciated. Thanks)

@@ijazali9736 It seems you would have to just check the list of live streams from RU-vid Live Streaming API periodically as there are no webhooks in its docs. But you could also experiment with RU-vid Data API that has something called "Push Notification" for video upload so that could maybe work with streams as well.

@@LuKillman Ok thanks I will play around with it.

For those cases an observer is a better tool than event listeners.

Well, the most straightforward way would be to check inside of the observer's method - if your condition is met, and then fire or not fire other events. Or, not sure if would work on Observers, or only events, but can you try Muting Events, or saveQuietly()? laravel.com/docs/8.x/eloquent#muting-events

@@PovilasKorop Thank you, Ill try it in practice)

You can't, observers are Eloquent function.

@@LaravelDaily if any other way.?

Events and Listeners

@@LaravelDaily can u make video on this one

One option is to create a UserObserver on email_verified_at field update.

@@PovilasKorop ok, i get it, thanks 😆