How fcakiroglu16/dotnet-microservices-course works
One.API accepts a user-creation request and publishes a shared event to RabbitMQ. Two.API and NotificationWorkerService independently consume that event and log the received user details. The README documents these service roles; the excerpts show the publish, queue binding, consumption, and acknowledgement behavior. No database-backed user persistence is shown.
Main entry points: Consumers/UserCreatedEventConsumer.cs Notification consumer · Program.cs User API · Consumers/UserCreatedEventConsumer.cs Two.API consumer · UserCreatedEvent.cs User-created event
Components 6
Event producer
- User API
One.API/Program.cs
Message broker
- RabbitMQ broker
Event consumers
- Two.API consumer
Two.API/Consumers/UserCreatedEventConsumer.cs - Notification consumer
NotificationWorkerService/Consumers/UserCreatedEventConsumer.cs
Shared contract
- User-created event
SharedLibrary/UserCreatedEvent.cs
Other components
- API client
Connections 9
- API client → User API: submits user
README.md - User API → User-created event: creates event
One.API/Program.cs - User API → RabbitMQ broker: publishes event
One.API/Program.cs - Two.API consumer → RabbitMQ broker: binds and consumes
Two.API/Consumers/UserCreatedEventConsumer.cs - Notification consumer → RabbitMQ broker: binds and consumes
NotificationWorkerService/Consumers/UserCreatedEventConsumer.cs - Two.API consumer → User-created event: deserializes event
Two.API/Consumers/UserCreatedEventConsumer.cs - Notification consumer → User-created event: deserializes event
NotificationWorkerService/Consumers/UserCreatedEventConsumer.cs - Two.API consumer → User API: registered by
- Notification consumer → Notification consumer: registered by
NotificationWorkerService/Consumers/UserCreatedEventConsumer.cs