gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Replace Github with GitHub (#34971)

Browse Source
This commit is contained in:
Lipis
2019-02-12 09:46:34 +01:00
committed by Randell Dawson
parent cd31f06c4b
commit 86b8cee810
48 changed files with 75 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
guide/english/javascript/async-messaging-with-rabbitmq-tortoise/index.md
View File

@ -12,7 +12,7 @@ Now a publisher typically publishes messages with a _routing key_ to something c
## Getting started
We're going to cook up a very simple example where a publisher script publishes a message to Rabbit, containing a URL, and a consumer script listens to Rabbit, takes the published URL, calls it and displays the results. You can find the finished sample up on [Github](https://github.com/rudimk/freecodecamp-guides-rabbitmq-tortoise).
We're going to cook up a very simple example where a publisher script publishes a message to Rabbit, containing a URL, and a consumer script listens to Rabbit, takes the published URL, calls it and displays the results. You can find the finished sample up on [GitHub](https://github.com/rudimk/freecodecamp-guides-rabbitmq-tortoise).
First, let's initialize a npm project:
@ -125,4 +125,4 @@ Here, we've told `tortoise` to listen to the `random-user-queue`, that's bound t
## Conclusion
The simplicity associated with using RabbitMQ for messaging is unparalleled, and it's very easy to come up with really complex microservice patterns, with just a few lines of code. The best part is that the logic behind messaging doesn't really change across languages - Crystal or Go or Python or Ruby work with Rabbit in pretty much the same way - this means you can have services written in different languages all communicating with each other effortlessly, enabling you to use the best language for the job.
The simplicity associated with using RabbitMQ for messaging is unparalleled, and it's very easy to come up with really complex microservice patterns, with just a few lines of code. The best part is that the logic behind messaging doesn't really change across languages - Crystal or Go or Python or Ruby work with Rabbit in pretty much the same way - this means you can have services written in different languages all communicating with each other effortlessly, enabling you to use the best language for the job.