AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

create public folder for images to reference and customize the tech radar

Browse Source
This commit is contained in:
dennis.ludwig
2021-06-14 13:45:42 +02:00
parent 80559fb632
commit 1d32f299c1
10 changed files with 7 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
radar/2017-03-01/rabbitmq.md
View File

@@ -11,5 +11,3 @@ There are several alternative solutions to RabbitMQ, e. g. the free Apache Activ
We use RabbitMQ internally for transferring messages safely in our logging ecosystem between [Logstash](/platforms-and-aoe-services/elk-stack.html) proxies and servers using direct and fan-out exchanges for delivering messages to appropriate destinations. RabbitMQ is also used to asynchronously trigger Jenkins jobs from our SCMs to mitigate heavy load on the SCMs, usually caused by Jenkins polls for SCM changes. Additionally, some critical events for monitoring are using RabbitMQ for guaranteed notification. 
RabbitMQ is rated "Trial". It fits into our approach to build robust, [resilient systems](/methods-and-patterns/resilience-thinking.html) and use [asyncronous messages](/methods-and-patterns/decoupling-infrastructure-via-messaging.html) for loosely coupled communications between components. In practice, RabbitMQ proved to be stable and dealt well with service interruptions from failures and maintenance slots. A common pain point is RabbitMQ as a single point of failure disrupting the data flow in a system. This issue is currently approached by setting up a HA cluster for RabbitMQ. The outcome of this approach will clarify the extent of future usage of RabbitMQ in our systems.
 ![](/assets/images/rabbitmq.png)