Menu
I am creating a Windows Service in C# that processes messages from a queue. I want to give ops the flexibility of partitioning the service in production according to properties of the message. For example, they should be able to say that one instance processes web orders from Customer A, another batch orders from Customer A, a third web or batch orders from Customer B, and so on.
My current solution is to assign separate queues to each customer\source combination. The process that puts orders into the queues has to make the right decision. My Windows Service can be configured to pull messages from one or more queues. It's messy, but it works.
976
Journal Queues store copies of messages. After sending a message, MSMQ can put a copy of the message in the Computer Journal (MachineName\Journal$). After removing a message from the destination queue, a copy of the message is optionally sent to the Queue Journal (MachineName\QueueName\Journal$).
Message Queuing (MSMQ) technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. Applications send messages to queues and read messages from queues.
No, but you can PEEK into the queue and decide if you really want to consume the message.
83
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
