I’d like to draw attention to this topic again.
Current status:
We all know that PHP’s performance leaves much to be desired because of its sync nature. PHP does not have a convenient and easy to use tool to do async\parallel programming.
The messaging API could help us here and opens new horizons for all of us PHP developers.
There is another problem: Nowadays everybody is building its own messaging library which is not compatible with others. The community is divided, loses the pace.
No way to build truly interoperable solutions which rely on messaging.
Solution:
I suggest starting with Java Message Service (JMS) specification. It was designed well and what is more important time-tested.
Here’s the implementation of the spec https://github.com/php-enqueue/psr-queue, we tried to be as close to it as it's possible.
Here's a bunch of transports implemented (such as AMQP, STOMP, Redis, Amazon SQS, Filesystem, Doctrine DBAL, Null)
I am looking forward to discussing it.
If you are a voting member and you think it worth it please consider supporting me (become a PSR sponsor).
Examples:
We’ll be able to build solutions, libraries based on it which is much more efficient.
Here are a few examples of what we could do (mostly from Symfony world):
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscribe@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/1b5e09e4-546f-4a83-9617-9cf35641033a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.