Last post Dec 01, 2017 05:38 AM by Fei Han - MSFT
Nov 30, 2017 07:16 PM|Alex9|LINK
Why MSMQ commonly preffered than simple console app with Queue?
Nov 30, 2017 07:32 PM|PatriceSc|LINK
It's for more advanced scenario. See https://en.wikipedia.org/wiki/Message_queue#Usage for a list of features such as durability etc...
If losing messages is ok a .NET Queue is fine.
If you want to persist them you could use a database.
If you want to handle priorities, have multiple instances consuming a message once, handle permissions etc... you could start to look closer at a message queuing system.
Dec 01, 2017 05:38 AM|Fei Han - MSFT|LINK
You can check the link that PatriceSc shared and
this link to know more about MSMQ. Besides, although the MSMQ is part of most Windows operating systems components, it is usually not installed as part of the default installation, so before using it we have to install it. If someone just want to store
a collection of objects in a queue for quick access, .NET Queue would be an easy and convenient approach.