-
Notifications
You must be signed in to change notification settings - Fork 6
[0.6] Laravel 10 and 11 support #79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Laravel 11 support
@clemblanco @oaklees please accept this PR so we can upgrade our laravel to v11 while still using laravel-aws-pubsub, please. |
Thanks @clemblanco for working so hard on this! |
Glad people are using our package @pierrekttipay Can you expend a bit more on how you use it, what for and how do you find it so far? |
Thanks for quickly actioning the request to review folks @clemblanco @oaklees. I will reply on behalf of @pierrekttipay with whom I work at https://kttipay.com/. We use this package for integrating with AWS EventBridge as the broker for event driven architecture in order to de-couple the modules in our system. This package is a perfect fit in the sense that it has a very minimal footprint and is based on the very awesome Laravel's broadcasting setup and ease of usage via the Laravel's event dispatcher. Initially, we used Laravel's event dispatcher as in-memory event broker without event bridge. However, we wanted a more reliable listener retry mechanism in case the listener fails and event bridge is great at that. All the event listeners are API Destination (pointing to the same Laravel app) with suitable retry configured and a Dead-Letter-Queue SQS for each listener configured if an event listener can't respond with 200 after continuous retries. I hope that makes sense. |
Uh oh!
There was an error while loading. Please reload this page.