You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2024-12-04-rabbitmq-connector.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Learn how to connect RabbitMQ to OpenFaaS to trigger functions from new and exis
18
18
19
19
### Introduction
20
20
21
-
When distributed systems need to run work in the background, developers often turn to message brokers like RabbitMQ, commit-logs like Kafka, or pub/sub systems like NATS. These components decouple the request from the response, allowing for asynchronous processing and scaling out to handle huge amounts of work.
21
+
When distributed systems need to run work in the background, developers often turn to message brokers like [RabbitMQ](https://www.rabbitmq.com/), commit-logs like Kafka, or pub/sub systems like NATS. These components decouple the request from the response, allowing for asynchronous processing and scaling out to handle huge amounts of work.
22
22
23
23
OpenFaaS supports event-driven architectures through the built-in asynchronous function concept, and through event connectors, to import events from external systems. In this post, we'll explore how to use the RabbitMQ connector for OpenFaaS to trigger functions from RabbitMQ queues.
0 commit comments