私人或公共MSMQ [英] Private or Public MSMQ

问题描述

我们正在使用Queue进行WCF服务中的少数服务. 我们正在为使用专用MSMQ的WCF服务使用NetMSMQ绑定. 该系统可以在我们的质量检查环境中正常运行. 我不确定私有队列和公共队列之间是否有真正的区别. 客户端应用程序在单独的机器上仍然能够访问其他框上的WCF服务的专用队列. 我不确定这是否正确. 私有MSMQ和公共MSMQ之间在安全性方面是否存在任何差异. 有人可以说明何时使用私有或公共MSMQ.

We are using Queue for few of are WCF services. We are using NetMSMQ binding for the WCF services which use Private MSMQ. The system works OK on our QA environment. I am not sure of any real difference between and private or public queue. The client application are on seperate machine still are able to access Private queue of the WCF service on other box. I am not sure if this is the right thing to do. are there any security related differences between private and public MSMQ. Can someone put some light on when to use Private or Public MSMQ.

推荐答案

我还建议使用专用队列.我从1.0版开始就使用MSMQ，并在AD集成之前进行了整个公共队列部署，并且在两种类型的公共队列部署上都做了工作，我认为私有队列方法最适合大多数组的需求.是的，整个企业消息传递的健壮性存在一些限制和差距，例如无法使用Routing Queue服务器，但是如果您的目标是简单地拥有一个不错的，可靠的消息传递平台来进行存储和转发以及使用在队列上触发，然后使用专用队列方法就可以了.我的小组每天通过专用队列处理超过300万条消息事务，并且已经这样做了很多年.

I also recommend using private queues. I've used MSMQ since version 1.0 and did the whole public queue deployment back before the AD intgration and having worked on both types of public queue deployment the private queue approach in my opinion is the best for most groups needs. Yes, there are some limitations and some gaps in overall enterprise messaging robustness, like not being able to use Routing Queue servers for example, but if your goal is to simply have a decent reliable message delivery platform for store-and-forward and use of triggers on queues then the private queue approach will be fine. My group processes well over 3 million message transactions per day through private queues and have been doing this for many years now.

这篇关于私人或公共MSMQ的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！