Skip to content
This repository has been archived by the owner on Sep 7, 2021. It is now read-only.

Laravel Innovations: Making your own webhook mechanism through notifications #85

Open
peterfox opened this issue May 31, 2018 · 2 comments

Comments

@peterfox
Copy link

https://medium.com/@SlyFireFox/laravel-innovations-making-your-own-webhook-mechanism-through-notifications-96e75e99a2b1

@RemiCollin
Copy link

Interesting use of notifications. What are the advantages of using this approach against a queued job that would call the API ?

@peterfox
Copy link
Author

@RemiCollin little to none except it makes a much more clear structure for delivery. It separates the who, what and where into notifiable, notification and channel. You can easily do the same thing with dispatching a job but then if you want to change or expand on that job you'll end up creating another job to sit along side the other. I'm sure there will be a few pros and cons for both ways tbh.

I just know I like using custom Channels to solve a few problems like that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants