.net NServiceBus 许可证?

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/5657809/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-09-03 15:28:42  来源:igfitidea点击:

NServiceBus license?

.netnservicebus

提问by Vaccano

Update:The most current licensing info can be found here: http://particular.net/licensing

更新:可以在此处找到最新的许可信息:http: //particular.net/licensing

So, I am reading the license restriction for NServiceBus Community Edition. It says:

所以,我正在阅读 NServiceBus 社区版的许可限制。它说:

Production use is limited to a single server with no more than 4 cores.

生产用途仅限于不超过 4 个内核的单个服务器。

Does that mean that all the subscribers and all the publishers need to be running on a single server?

这是否意味着所有订阅者和所有发布者都需要在单个服务器上运行?

Or does it mean that each server that is either a publisher or a subscriber can have no more than 4 cores?

或者这是否意味着作为发布者或订阅者的每个服务器不能超过 4 个内核?

I am hoping it is the later as we had planned to use NServiceBus to allow several applications (and services) running on several different client machines and servers to subscribe to business events. I would be hard pressed to get my management to pay $500 for every cpu on every machine that we want to allow as a subscriber to a published event.

我希望它是后者,因为我们计划使用 NServiceBus 来允许在几个不同的客户端计算机和服务器上运行的多个应用程序(和服务)订阅业务事件。我很难让我的管理层为我们希望允许作为已发布事件的订阅者的每台机器上的每个 CPU 支付 500 美元。

UPDATE: As a side note, the commercial license says that they "will have the right to enter Your premises and access Your records and computer systems" to make sure you are paying the full amount. I know my data security people are going to choke a bit on that. Does anyone who have the commercial version have a comment on how often this audit happens and how intrusive it really is?

更新:附带说明,商业许可证说他们“将有权进入您的场所并访问您的记录和计算机系统”,以确保您支付全额费用。我知道我的数据安全人员会对此感到有些哽咽。任何拥有商业版本的人都对这种审计发生的频率以及它的真正侵入性有什么意见吗?

回答by Vaccano

UPDATE: The licensing for NServiceBus seems to have changed for version 4.0. I can't find anything about an Express Version. This mostly likely does not apply to that version.

更新:NServiceBus 的许可似乎在 4.0 版中发生了变化。我找不到有关 Express 版本的任何信息。这很可能不适用于该版本。

So I dug into this more for the 2.5 version of NServiceBus.

所以我在 NServiceBus 的 2.5 版本中更深入地研究了这一点。

NServiceBus has three licenses options (that apply to both codeand binaries) that I interpret as follows:
(DISCLAIMER: I am not a lawyer so read the real licenses and follow those)

NServiceBus 有三个许可证选项(适用于代码二进制文件),我解释如下:(
免责声明:我不是律师,所以阅读真正的许可证并遵循这些)

  • RPL 1.5:The Open Source "like" license. This has a big limitation to it. That limitation is that you have to post all "DerivativeWorks" back out to the net. The folks over at GNU listthis as a Non-Freelicense. (Though if your project is open source then this license keeps NServiceBus "free" (in effect)).

    Update:Udi Dahan states that "Derivative works do not include code which make use of NServiceBus as a library (binding to the external interface)."(This has been clarified to not be true. See below.)

    Another Update:Phill says he emailed Udi and he was told that the license does not work like that. (See his comment below)

    I admit that while I thank Udi for his great product, but I wish he would get his licensing straightened out and made a bit clearer.

    Yet Another Update:Udi responded to my question again and admitted that he was basing his earlier comment off of the previously used Apache License. The new licensing uses RPL and basically means that if you can't release the source that uses NServiceBus under RPL then you can't use NServiceBus as RPL.

  • Express Edition:You can use it for free with these limitations:

    1. All the publishers and subscribers are:
      • On one (the same) machine (meaning you can have NServiceBus only running on one box)
      • And that machine has no more than 4 cores.
        (You can't have a distributed model at all with this license.)
    2. You only can have one worker thread with this license.
  • RPL 1.5开源“喜欢”许可证。这对它有很大的限制。该限制是您必须将所有“衍生作品”发布回网络。GNU的人们其列为自由许可证。(尽管如果您的项目是开源的,那么此许可证使 NServiceBus 保持“免费”(实际上))。

    更新:Udi Dahan 声明“衍生作品不包括使用 NServiceBus 作为库(绑定到外部接口)的代码。” (这已被澄清为不正确。见下文。)

    另一个更新:Phill 说他给 Udi 发了电子邮件,他被告知许可证不能那样工作。(见下面他的评论)

    我承认虽然我感谢 Udi 的出色产品,但我希望他能够理顺他的许可并使其更加清晰。

    另一个更新:Udi 再次回答了我的问题,并承认他之前的评论是基于之前使用的 Apache 许可证。新的许可使用RPL,基本上意味着如果您不能在RPL 下发布使用NServiceBus 的源代码,那么您就不能将NServiceBus 用作RPL。

  • Express Edition:您可以免费使用它,但有以下限制:

    1. 所有发布者和订阅者是:
      • 在一台(同一台)机器上(意味着您只能在一台机器上运行 NServiceBus)
      • 而那台机器的内核不超过 4 个。
        (使用此许可证根本不能拥有分布式模型。)
    2. 您只能拥有一个具有此许可证的工作线程。

  • Standard Edition:
    1. You pay $500 per core (or $25/month/core) for as many servers as you need to allow high performance (more than one worker thread). You must buy at least one.
    2. You get to use the Express License (as outlined above) without the limitations of #1 (single machine and 4 cores)
    3. The folks at NServiceBus get to come and "enter Your premises and access Your records and computer systems" on an annual basis to validate that you are paying what you should be paying.
  • 标准版:
    1. 您需要为每个内核支付 500 美元(或每月 25 美元/内核),购买尽可能多的服务器以实现高性能(多于一个工作线程)。你必须至少买一个。
    2. 您可以使用 Express 许可证(如上所述)而不受 #1(单机和 4 核)的限制
    3. NServiceBus 的人每年都会来“进入您的场所并访问您的记录和计算机系统”,以验证您是否支付了应支付的费用。

So, if you want unlimited use of the Express Edition then the best best is to buy 1+ core licenses under the Standard Edition. You can then use as many Express Edition licenses as you like.

因此,如果您想无限制地使用 Express Edition,那么最好购买 Standard Edition 下的 1+ 核心许可证。然后,您可以根据需要使用任意数量的 Express Edition 许可证。

Sources
Here are my sources for this post. They mostly come from quotes from Udi Dahan, the "owner and author" of NServiceBus:

来源
这是我这篇文章的来源。它们主要来自 NServiceBus 的“所有者和作者”Udi Dahan 的引述:

NOTE: NServiceBus is still cheaper than most of the ESB players out there. And far far cheaper than rolling your own.

注意:NServiceBus 仍然比大多数 ESB 播放器便宜。而且比自己动手便宜得多。

回答by Phill

Edit: Licensing has changed so this is no longer true. :(

编辑:许可已更改,因此不再适用。:(

NServiceBus is still free if you want to download and compile the source, theres no restrictions on it.

如果您想下载和编译源代码,NServiceBus 仍然是免费的,没有任何限制。

The licenses you buy are for commercial support.

您购买的许可证用于商业支持。

If you download/compile it yourself then you can only rely on yourself and the community to solve issues and look for help.

如果您自己下载/编译它,那么您只能依靠自己和社区来解决问题并寻求帮助。

Buying a license you get restrictions on what you can run NServiceBus on, but the commercial support.

购买许可证后,您将获得运行 NServiceBus 的限制,但获得商业支持。

(i hope that makes sense)

(我希望这是有道理的)

Edit:Yes, when Udi Dahan did he training course end of Sydney last year, the issue around licensing was asked during a talk he did afterward, he said NServiceBus is still free and open source, however some companies wont use it because there is no commercial support.

编辑:是的,当 Udi Dahan 去年在悉尼结束培训课程时,在他之后的一次演讲中提出了有关许可的问题,他说 NServiceBus 仍然是免费和开源的,但是有些公司不会使用它,因为没有商业支持。

So if you download/compile yourself, its free but you are on your own in terms of support.

因此,如果您自己下载/编译,它是免费的,但就支持而言,您是靠自己的。

If you download it via the website, you will get limited support via the express edition, and buying a commercial license you will get more support, but you are locked down to the servers on the site.

如果您通过网站下载它,您将通过 express 版本获得有限的支持,购买商业许可证您将获得更多支持,但您被锁定在网站上的服务器上。

http://sydney.ozalt.net/2010/11/november-meeting-recorded-for-your.html

http://sydney.ozalt.net/2010/11/november-meeting-recorded-for-your.html

Video ^ 1 hour 23 minutes in the video is the talk of commercial support.

视频 ^ 视频中的 1 小时 23 分钟是关于商业支持的讨论。

http://www.philliphaydon.com/2010/12/sydney-alt-net-with-udi-dahan-and-nservicebus-commercial-support/

http://www.philliphaydon.com/2010/12/sydney-alt-net-with-udi-dahan-and-nservicebus-commercial-support/

回答by Joey V.

If you're concerned with the new licensing, you can use NSB version 2.0. It's licensed under Apache v2.

如果您担心新的许可,您可以使用NSB 2.0 版。它在 Apache v2 下获得许可。

You may run into some dependency issues with old third-party libraries being older. Grab the source from GitHuband recompile with the new versions.

由于旧的第三方库较旧,您可能会遇到一些依赖性问题。从GitHub获取源代码并使用新版本重新编译。