JBoss EAP 6.1与Tomcat 7 [英] JBoss EAP 6.1 vs Tomcat 7

问题描述

我们有一个使用JSF 2.0，Spring，Hibernate，MySQL数据库的Web应用程序。它正在开发中，很快就会投入生产。我们将来可能不得不部署一些Web服务（只有一点点机会，直到我们投入生产才会确认）。

我们正在考虑将Tomcat和JBoss EAP 6.1 Alpha用于生产部署。
我一直在读Tomcat在制作中被广泛使用，并且没有太多争议。

有趣的是，JBoss EAP 6.1 Alpha（社区支持不推荐用于生产的JBoss版本。建议是去商业版。以下是关于在这两者之间作出决定的思考过程。

1. 两者都是开源和社区支持的


2. 两者都可以免费使用


3. 两者都已存在一段时间


4. Apache和RedHat（社区版本）都做了不提供支持包

如果Tomcat工作，为什么不能使用JBoss EAP 6.1 Alpha？简单地说Tomcat比JBoss EAP 6更成熟吗？

注意：如果没有要求（虽然没有在momemt中确认）开箱即用的Web服务和JTA的支持，我们会选择Tomcat而不再考虑。

我的问题是为什么JBoss EAP 6.1 Aplha而Tomcat 7没问题？

解决方案

免责声明：这只是我的看法。我不以任何方式与JBoss有关联。

我认为不推荐用于生产的原因是缺乏支持合同，与产品无关。他们在常见问题页面上说

第一个EAP阶段Alpha与
社区最终版本具有相同或更好的质量。

和

7.2.0.Final始终是EAP 6.1.0.Alpha的基础。由于
新的6.1.0.Alpha的广泛可用性，并且为了简单起见，
我们发布了一个名为EAP 6.1.0.Alpha的版本。

因此，假设社区最终版本可用于生产，我认为没有任何直接原因eap 6.1.alpha无法用于生产。

但是，通过支持合同，您将获得支持联系人以及针对此版本所做的错误修复。据我所知，没有针对eap 6.1.alpha的错误修复，但已经有EAP 6.1.1版本修复了一些错误。这是您进入生产时需要考虑的重点。

---

更新：如果您想继续使用AS7并继续对于具有错误修复的生产，可以选择从源构建EAP。引用此消息：

基本上我们给你三个选择：

1. 坚持社区 - 你总是得到最新的和最前沿的东西（包括实验性功能），但你需要
   获得社区的支持并更频繁地更新，因为
   社区真的只专注于最新的主要+次要版本。




2. 购买EAP订阅 - 您可以获得上述所有功能，从而最大限度地减少您在app server
   维护和支持上花费的工作量。




3. 自构建和支持EAP - 您可以获得企业版本的一些好处（例如旧版主要版本的补丁等），
   但是你必须投入时间和精力来构建和维护/验证你的应用服务器分配位
   。

如果有人想要使用第三个选项，则来源位于 ftp://ftp.redhat.com/redhat/jbeap/

We have a web application that uses JSF 2.0, Spring, Hibernate, MySQL database. It is under development and soon will go into production. We might have to deploy some web services in the future (only a little chance and it would not be confirmed until we go into production).

We are considering Tomcat and JBoss EAP 6.1 Alpha for the production deployment. I have been reading that Tomcat is being used in Production extensively and there is not much dispute about it.

Interestingly, JBoss EAP 6.1 Alpha (the community supported version of JBoss) is NOT recommended for production. The recommendation is to go for the commercial version. Here is my thought process around making a decision between these two.

1. Both are open source and community supported
2. Both are free to use in production
3. Both have been around for a while
4. Both Apache and RedHat (on the community versions) do NOT provide support packages

If Tomcat works, why not JBoss EAP 6.1 Alpha would work? Is it simply that Tomcat is more mature than JBoss EAP 6?

NOTE: If there is no requirement (not cofirmed at the momemt though) for out of the box Web Services and JTA support, we would go with Tomcat with no second thoughts.

My question is why not JBoss EAP 6.1 Aplha while Tomcat 7 is ok?

解决方案

Disclaimer: this is just my view. I'm not affiliated with JBoss in any way.

I think the reason it is not recommended for production is the lack of support contract, nothing related to product as such. They say on the FAQ page that

The first EAP stage Alpha is of equivalent, or better, quality to a community Final release.

and

7.2.0.Final was always the basis for EAP 6.1.0.Alpha. Due to the new wide-availability of 6.1.0.Alpha, and for simplicity reasons, we've released just one release called EAP 6.1.0.Alpha.

So assuming community final releases can be used in production, I don't see any direct reason eap 6.1.alpha couldn't be used in production.

With a support contract however, you get support contacts and the bug fixes that have been made for this release. There are no bug fixes against eap 6.1.alpha as far as I know, but there already is EAP 6.1.1 release with some bug fixes. That's an important point to consider when you go to production.

---

Update: if you want to keep on using AS7 and go to production having the bug fixes, there is an option of building the EAP from sources. Quoting this message:

Essentially we give you three choices:

1. Stick with community - You get always get the latest and greatest cutting edge stuff (including experimental features), but you have to get support from the community and update more frequently since the community really only focuses on the latest major + minor version.

2. Buy an EAP subscription - You get all of the features above, which lead to minimizing the amount of work you need to spend on app server maintenance and support.

3. Self build and support EAP - You get some of the benefits of the enterprise releases (e.g. patches to older major versions and so on), but you have to invest time and energy to build and maintain/verify your app server distribution bits.

Should anyone want to go with the third option, the sources are at ftp://ftp.redhat.com/redhat/jbeap/

这篇关于JBoss EAP 6.1与Tomcat 7的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！