Discusses KAKFA do Message Queuing and Redis implement Message Queuing differences

When Redis does Message Queuing, consider two types of data structures: List and zset.
But in this case, Message Queuing is a point-to-point structure that requires a task to loop the Lpop element, but will this second level of request feel like a Redis?

Kafka words are really good, but the price is relatively large?

What are the good methods of Message Queuing for everyone?

Reply to discussion (solution)

Kafka itself is Message Queuing, which is certainly more advantageous than Redis, and you mean the cost of learning or deployment.

I think to see their own business scenario, if it is a very common business scenario, the amount of data concurrency is small, with what is similar.

If you require a very high architecture, Kafka is more appropriate, and also supports distributed.

PS, I haven't used Kafka much, our company use rabbitmq~

Kafka itself is Message Queuing, which is certainly more advantageous than Redis, and you mean the cost of learning or deployment.

I think to see their own business scenario, if it is a very common business scenario, the amount of data concurrency is small, with what is similar.

If you require a very high architecture, Kafka is more appropriate, and also supports distributed.

PS, I haven't used Kafka much, our company use rabbitmq~

Ox, I haven't touched RABBITMQ, I've just heard of it.
Because I rented the Ali server, I feel it is not very meaningful to build a single Kafka. I would like to use the Redis list, but Blpop and Lpop are measured, still have to use lpop more appropriate, but I myself worry, such a while type of operation, has been in the request to Redis, will give the server a lot of pressure?

