NServiceBus许可证? [英] NServiceBus license?

查看:757
本文介绍了NServiceBus许可证?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

更新:的最新许可信息可以在这里找到: http://particular.net /许可

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

  

生产的使用仅限于单个服务器具有不超过4个核。

这是否意味着所有用户和所有的发布者需要在一台服务器上运行?

或者这意味着每个服务器可以是发布者或订阅者可以有不超过4个内核?

我希望这是后来的,因为我们曾计划使用NServiceBus允许多个应用(服务)在几个不同的客户机和服务器上运行的订阅业务事件。我会pssed让我的管理支付$ 500每台机器上的每个CPU,我们要允许一个用户到发布的事件很难$ P $。

更新: 作为一个侧面说明,商业授权说,他们将要进入你的premises并访问您的记录和计算机系统的权利,以确保您支付的全部金额。我知道我的数据的安全性,人们会呛了一下这一点。有谁谁拥有商业版有评论多久这次审计情况,以及如何侵入它真的是?

解决方案

更新:许可NServiceBus似乎已经改变了4.0版本。我无法找到一个防爆preSS版本什么。这主要可能并不适用于该版本。

所以,我挖成这种多为2.5版本的NServiceBus的。

NServiceBus有三个许可证选项(即适用于 code 和的binaries ),我跨preT如下:
(免责声明:我不是律师,所以读真正的许可证,并按照此)

  • RPL 1.5 开源喜欢许可。这有一个很大的限制了。这限制是,你必须张贴所有的<一个href="http://stackoverflow.com/questions/5658672/what-does-using-a-project-that-has-the-reciprocal-public-license-1-5-mean-i-hav">Derivative 作品背出净。该伙计在 GNU列表这是一个非的Free 许可证。 (不过,如果你的项目是开源则此许可证保持NServiceBus自由(有效))。

      

    更新: 乌迪大汉指出,衍生作​​品不包括code的使用NServiceBus作为库(绑定到外部接口)。 (这已被澄清,不是真实的,见下图。)

         

    另一个更新:菲尔说,他通过电子邮件发送乌迪,他被告知,该许可证不这样的。 (见下面他的评论)

         

    我承认,虽然我感谢乌迪对他的伟大的产品,但我希望他能得到他的许可理顺,并提出了更清楚一点。

         

    然而,另一个更新:乌迪回答我的问题再次承认他是根据他先前的评论关闭previously使用Apache许可证。新的许可使用RPL,基本上意味着,如果你不能释放,使用NServiceBus RPL下源,那么你不能使用NServiceBus为RPL。

  • 防爆preSS版::您可以免费使用它具有以下限制:

    1. 所有的发布者和订阅者:
      • 在一(下同)的机器(这意味着你可以有NServiceBus只能运行在一个盒子)
      • 这机器有不超过4个内核。
        (你不能有一个分布式模型在所有与该许可。)
    2. 您只能有一个工作线程与此许可证。

  • 标准版:
    1. 您支付$ 500核心(或$ 25 /月/核心),因为你需要让高性能(多个工作线程)为尽可能多的服务器。你必须至少购买一种。
    2. 您获得使用防爆preSS许可证(如上文所述),而不#1(单台机器和4芯)
    3. 的限制
    4. 伙计在NServiceBus让前来输入您的premises并访问您的记录和计算机系统每年来验证你付出什么,你应该得到回报。

所以,如果你想无限使用防爆preSS版的话,最好最好是买1 +内核许可下的标准版。然后,您可以根据需要使用尽可能多的防爆preSS版许可证。

来源
这里有我的消息来源为这个职位。他们大多来自报价从乌迪大汉,NServiceBus的所有者和作者:

请注意: NServiceBus仍比大多数ESB球员那里便宜。而且远远比便宜滚动你自己的。

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

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

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

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?

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.

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?

解决方案

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.

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

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

  • RPL 1.5: The Open Source "like" license. This has a big limitation to it. That limitation is that you have to post all "Derivative Works" back out to the net. The folks over at GNU list this as a Non-Free license. (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.

  • 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.

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.

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

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

这篇关于NServiceBus许可证?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆