How ssmaciel/dotnet_rabbitmq_redis works
This repository is a small RabbitMQ messaging demo with an ASP.NET API and multiple message consumers. A POST to the API publishes a serialized message; hosted workers and a console consumer read from the InfoFila queue and acknowledge deliveries. The API also has an independent forecast GET endpoint. The supplied source shows the API’s exchange and routing-key configuration and the consumers’ queue, but not queue bindings or deployment wiring, so those links are not inferred.
Main entry points: WeatherForecastController.cs Forecast endpoint · WorkerService1/Program.cs Worker host · API/Program.cs API host · Worker1.cs Worker 1
Components 10
HTTP API
- API host
API/Program.cs - Forecast endpoint
API/Controllers/WeatherForecastController.cs - Forecast model
API/WeatherForecast.cs
Messaging
- RabbitMQ broker
Consumers
- Worker host
WorkerService1/Program.cs - Worker 1
WorkerService1/Worker1.cs - Worker 2
WorkerService1/Worker2.cs - Console entry
ConsoleApp1/Program.cs - Console consumer
ConsoleApp1/RabbitConsummercs.cs
Other components
- HTTP client
Connections 11
- HTTP client → API host: HTTP request
- API host → Forecast endpoint: dispatches
- Forecast endpoint → Forecast model: creates
- Forecast endpoint → HTTP client: returns forecast
- Forecast endpoint → RabbitMQ broker: publishes message
- Worker host → Worker 1: hosts
- Worker host → Worker 2: hosts
- Worker 1 → RabbitMQ broker: consumes and acknowledges
- Worker 2 → RabbitMQ broker: consumes and acknowledges
- Console entry → Console consumer: calls
- Console consumer → RabbitMQ broker: consumes and acknowledges