Skip to content
Convention Over Configuration: Queueing is Easy
- Queuing is intimidating
- Quick review of queueing
- processing that isn’t web or db can be pushed to another server and not impact ui or db server or make users wait for processing finish(async)
- Introduce a queue instead of managing async communication on our won
- We take request from user, tell them we will get back to them stick request on queue
- can scale processors taking work off the queue when needed
- RabbitMQ on .NET demo
- reviewed basic of running rabbitmq on .net
- rabbit messages are byte arrasy so have to serialize payload to byte array
- have to acknowledge receipt, basicAck, or message will stay in queue.
- Queuing patterns with EasyNetQ
- .net tool only
- Tool that sits on top of rabbitMQ
- provides common queuing patters right out of box eliminating need to do deep configuration and serialization and deserialization of messages.
- can think of messages as objects now, no need to get to byte array on your own
- best of .net on both client and receiver
- common patterns
- Send and Receive
- send message to a receiver, duh.
- Publish and subscribe model
- publisher puts message on queue doesn’t care who is listening
- subscribers listen to what interests them
- Request and Response
- put request on request queue
- put response on response queue