不使用基于云的资源的集中式 Pub Sub 选项

发布于 2024-11-04 09:27:36 字数 488 浏览 6 评论 0原文

是否存在集中式但不使用任何基于云的产品的 .Net 兼容 Pub/Sub 工具?

我研究过 NServiceBus,它是 Pub/Sub 的领跑者,但我不喜欢它在每台机器上放置的基础设施数量。

我更喜欢有一个集中的选项,我有一个强大的服务器来处理所有发布和订阅操作,并在发布者发送订阅者需要获取的消息时简单地进行所需的调用。 (有点像亚马逊的消息服务。)

我可以将 NServiceBus 包装在这样的系统中,但如果已经有一个好的解决方案,我宁愿不这样做。

如果您想知道为什么我对云选项说“不”,我在一家医疗公司工作,通过网络发送受保护的健康信息的问题根本不值得将其卸载到云的好处。另外,如果出现故障,我需要将其归咎于我们的错误,并让修复工作在我们的控制之下。

(注:我正在寻找 10,000 美元以下的解决方案。像 Tibco 这样的东西很棒,但它们只是超出了我的价格范围。)

Are there .Net compatible Pub/Sub tools out there that are centralized, but don't use any cloud based offerings?

I have looked at NServiceBus and it is the Pub/Sub front runner, but I don't like the amount of infrastructure it puts on each machine.

I would prefer to have a centralized option where I have a beefy server that handles all publish and subscribe actions and simply makes the needed calls when a publisher sends a message that a subscriber needs to get. (Kind of like Amazon's messaging service.)

I could wrap NServiceBus up in a system like that, but I would rather not do that if there is a good solution out there already.

In case you are wondering why I said "no" to the cloud option, I work for a medical company and the issues of sending Protected Heath Information over the web are just not worth the benefits of offloading this to the cloud. Also, if it goes down, I need it to be our fault and have the fix be under our control.

(NOTE: I am looking for solutions in the under $10,000 range. Things like Tibco are great, but they are just out of my price range.)

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

长亭外,古道边 2024-11-11 09:27:36

您正在寻找消息代理,这通常不是 ESB 的发展方向,因为代理在高吞吐量/可用性场景中很快就会成为瓶颈。 MassTransit 是 NServiceBus 的替代方案,Rhino Service Bus 也是如此。

我个人正在等待 ESB 框架开始出现,这些框架要么为其消息传递架构提供可插入框架,要么围绕 ProtoBuf、zeroMQ 或 RabbitMQ 构建。除了 MSMQ 之外的任何东西。公共交通应该很快就会支持 RabbitMQ(tm)...

You're looking for a message broker, which isn't generally the direction that ESBs have gone since the broker becomes a bottleneck very quickly in a high throughput/availability scenarios. MassTransit is an alternative to NServiceBus, as is Rhino Service Bus.

I am personally waiting until ESB frameworks start coming out that either have a pluggable framework for their messaging architecture or are built around ProtoBuf or zeroMQ or RabbitMQ. Anything but MSMQ. Mass Transit should have RabbitMQ support sooon(tm)...

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文