I am really starting with Message Queue and I am looking for very basic information, how to's and so on.
But I have a strange sensation with what I am finding. It seems "Message Queue Server" is not the "standard" way of do in Visual Studio 2010, Windows 7, or the very last products from Microsoft, because all information I am finding is related to old microsoft products. Or that is my first impression.
In fact: http://www.microsoft.com/msmq/ doesn't run. It is empty ?
In summary: I don't know why... but I think Message Queue from Microsoft is not a "cutting edge" product to put my efforts on and perhaps there is another substitution product. Is it true or I am mistaken ?
What new product offers the same functionality nowadays ?
Thanks.
Unlike a message queue, Kafka enables you to publish messages (or events) to Kafka topics. These messages will not be removed when a consumer retrieves them, making them persistent messages.
Message queues provide communication and coordination for these distributed applications. Message queues can significantly simplify coding of decoupled applications, while improving performance, reliability and scalability. You can also combine message queues with Pub/Sub messaging in a fanout design pattern.
It is used in old products, but I've never had any reason to think it as deprecated.
One example of where the message queue is supported is WCF.
There isn't any other way to send one-way messages to a WCF server which you know will arrive even if the server is down at sending time.
MSMQ is alive and well. We use it in production when we need reliable delivery but NOT interactive/realtime responses. Its also integrated with WCF.
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