-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
Symfony Messenger Integration #438
Comments
OK, but we're not Symfony core maintainers. Are you looking for our approval, or something? |
I mean only you could describe the benefits of using amp library the best way possible. I'd like to ask you to create the issue for symfony so that amp integration could be implemented by their core team Thank you |
Nobody is going to fight your battles for you.
Symfony already uses Amp. You may find it's not a hard sell.
…On Tue, 23 Apr 2024, 20:03 Yevhen Sidelnyk, ***@***.***> wrote:
I mean only you could describe the benefits of using amp library the best
way possible.
I'd like to ask you to create the issue for symfony so that amp
integration could be implemented by their core team
Thank you
|
Yes, you are 💯 right Closing this issue for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there!
I'm really excited about third version of this library and specifically that it doesn't struggle with red/blue functions problem.
Great thumbs up for such a great library!
As far as I know, there isn't any known open-source solution that integrated amphp into Symfony Messenger (please, correct me if I'm wrong).
What I think, it would really make a lot of sense having the ability to take up N (for instance 16) messages from the queue and run their processing in async manner. When dealing with sluggish-slow third-party APIs that could respond 30 seconds, this approach would've extremely increased the overall system performance.
I think, one shall propose this approach to symfony core maintainers, since having it is really reasonable
The text was updated successfully, but these errors were encountered: