For large PHP applications, what applications are usually used for message queue?

I have been using Redis for Message Queue. I suddenly thought, will it be better? I have been using Redis for Message Queue. I suddenly thought, will it be better? Reply content: We use beanstalk, qps1000 or so. if it is a simple queue service, we suggest beanstalkd (small, good performance). if it is high-availability and massive, kafka can be used. It is better to first point out what aspects of the existing solution are not good enough. Does this problem have nothing to do with PHP? More business scenarios are considered for the selection of message queues:

* Performance, such as the number of messages per second. if you have tens of thousands of messages per second, the Beanstalk and RabbitMQ columns cannot be used directly.
* Reliability: can messages be lost? Persistence required?
* High Availability: Can I tolerate downtime?
* Need to be distributed?
* O & M costs: Is your company's development (O & M) capable of maintaining this message queue?
* Supported by the client. this is the language level. For example, Kafka is a good message queue, but its PHP client is not well written and it is difficult to re-write it by yourself. Therefore, you must be careful when selecting Kafka.

After balancing these factors, we can determine how to choose.
Message queue
Performance Comparison: http://bravenewgeek.com/dissecting-message-queues/ Redis and rabbitmq use redis and rabbitmq depending on your application scenarios. generally, redis is relatively simple, but redis cannot process messages normally, other processes can still process the message, that is, there is no process to complete the confirmation of the message.
For a complete message queue, gearman and rabbitmq are all good. Php-resquegearman. If you want to avoid message loss across networks, you can also select kafkaworkerman