|
@@ -1289,11 +1289,11 @@ Message queues receive, hold, and deliver messages. If an operation is too slow
|
|
|
|
|
|
The user is not blocked and the job is processed in the background. During this time, the client might optionally do a small amount of processing to make it seem like the task has completed. For example, if posting a tweet, the tweet could be instantly posted to your timeline, but it could take some time before your tweet is actually delivered to all of your followers.
|
|
|
|
|
|
-**Redis** is useful as a simple message broker but messages can be lost.
|
|
|
+**[Redis](https://redis.io/)** is useful as a simple message broker but messages can be lost.
|
|
|
|
|
|
-**RabbitMQ** is popular but requires you to adapt to the 'AMQP' protocol and manage your own nodes.
|
|
|
+**[RabbitMQ](https://www.rabbitmq.com/)** is popular but requires you to adapt to the 'AMQP' protocol and manage your own nodes.
|
|
|
|
|
|
-**Amazon SQS**, is hosted but can have high latency and has the possibility of messages being delivered twice.
|
|
|
+**[Amazon SQS](https://aws.amazon.com/sqs/)** is hosted but can have high latency and has the possibility of messages being delivered twice.
|
|
|
|
|
|
### Task queues
|
|
|
|