Microsoft.ServiceBus.Messaging与Microsoft.Azure.ServiceBus [英] Microsoft.ServiceBus.Messaging vs Microsoft.Azure.ServiceBus

问题描述

MS最近引入了 Microsoft.Azure.ServiceBus 名称空间.
https://github.com/Azure/azure-service -bus/blob/master/samples/readme.md

MS has recently introduced the Microsoft.Azure.ServiceBus namespace.
https://github.com/Azure/azure-service-bus/blob/master/samples/readme.md

它适用于新的 .net标准框架(好像MS没有足够的半冗余代码库)

It is geared for the new .net standard framework (as if MS doesn't have enough semi-redundant code bases)

我的问题是，在性能方面有什么改善?

My question is, how much better could it be in terms of performance?

我可以自信地说， Microsoft.ServiceBus.Messaging 有很多不足之处，尤其是在持久接收方面.

I can say with confidence, that the Microsoft.ServiceBus.Messaging leaves lots to be desired, in particular when it comes to persistent receiving.

Microsoft.ServiceBus.Messaging 的一项非常有用的功能是在 OnMessage()方法之上构建的消息泵.

A very useful feature of the Microsoft.ServiceBus.Messaging , is the message pump, built on top of OnMessage() method.

新库没有此库，需要在每张收据上重新绑定事件处理程序以保持运行.绝对要后退.

The new library, doesn't have this, and needs to rebind event handlers on every receipt to keep pumping. Definitely a step backward .

正在寻找既有两者经验又可以比较的人的反馈.

Looking for feedback from anyone who has had experience with both and can compare..

推荐答案

要解决您的问题，.netstd库提供的内容不在.netframework one中.

To address your question, what .netstd library offers that was not in .netframework one:

1. 开源.新库是完全开源的.您无需设置符号服务器即可浏览，进入(在下一版本中)，进行贡献，仅查看工作方式.
2. 与.netframework库相反，新库确实是异步的.
3. 减少的责任数量和代码大小.例如， Message 与BrokeredMessage.您的数据不再由客户端序列化.
4. 默认情况下是AMQP，而不是SBMP.
5. 新客户端瞄准插件和可扩展性，经过全面测试.

1. Open Source. The new library is fully open sourced. You can browse, step into (with the next release) without setting up symbols server, contribute, and simply review how things work.
2. The new library is truly async as oppose to what the .netframework library was.
3. Reduced amount of responsibilities and code size. For example, Message vs BrokeredMessage. Your data is no longer serialized by the client.
4. AMQP by default and not SBMP.
5. The new client targets .NET Standard and Full Framework.
6. Certain client aspects redesigned to provide better options (OnMessage API to provide more failure context, plugins and extensibility, interfaces for easier testing).
7. Fully tested.

在性能方面，如果不是更好的话，应该与老客户保持一致.

Performance wise it should be on par with the old client if not better.

Microsoft.ServiceBus.Messaging的一个非常有用的功能是在OnMessage()方法之上构建的消息泵.

A very useful feature of the Microsoft.ServiceBus.Messaging , is the message pump, built on top of OnMessage() method.

您仍然拥有OnMessage API，尽管已重命名为

You still have OnMessage API, though renamed to RegisterMessageHandler.

这篇关于Microsoft.ServiceBus.Messaging与Microsoft.Azure.ServiceBus的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！