问题描述
我目前正在开始新的应用开发。应用程序架构师坚持认为我们使用 JBoss5 ，因为它更好。有没有人对更好有更广泛的定义（如果是这样的话）？
I'm currently starting a new app development. The app architect insists we use JBoss5 because its "better". Do anyone has a wider definition of "better" (if its the case)?
我有使用 Tomcat5 和6的经验，在大用户负载的大型应用程序中运行得非常好（恕我直言）。两者都将在相同的硬件条件下运行 RedHat6 （如果实施很重要）。
I have experience using Tomcat5 and 6 in large scale applications with big user loads and it handles pretty well (IMHO). Both would be running over a RedHat6 in identical hardware conditions (in case the implementation matters).
提前致谢
推荐答案
要说任何工具或框架只是'更好'是荒谬的。它总是取决于情况，建筑等。你不一定要用锤子来驱动螺丝。
To say that any tool or framework is just 'better' is ridiculous. It always depends on the situation, architecture, etc. You don't necessarily want to use a hammer to drive a screw.
我在Action中编写了JBoss，所以我显然喜欢JBoss技术，但我会第一个说JBoss在许多情况下可能会过度杀伤。例如，对于我开发的最后两个站点，使用Grails构建并在独立的Tomcat实例上部署更有意义。
I wrote JBoss in Action, so I obviously like the JBoss technology, but I'll be the first to say that JBoss can be overkill in many situations. For example, for the last two sites I've developed, it made more sense to build with Grails and deploy on a standalone Tomcat instance.
说它有点不公平使用JBoss时得到的只是EJB和JMS。 JBoss提供了许多服务和功能，包括：
Its a bit unfair to say that all you get when using JBoss is EJB and JMS. JBoss offers many services and features, including:
- Servlet / JSP容器
- JNDI
- EJB
- JTA
- 集群
- 缓存
- JMS
- 数据源/资源管理
- JMX集成
- OSGi支持
- 网络服务
- 门户网站
- 网络豆（Seam）
- 一些管理控制台
- 一个IoC容器
- 等。
- Servlet/JSP container
- JNDI
- EJB
- JTA
- clustering
- caching
- JMS
- Datasource / Resource management
- JMX integration
- OSGi support
- web services
- portals
- Web Beans (Seam)
- Some administrative consoles
- an IoC container
- etc.
吸引许多建筑师加入JBoss的是它的灵活性。它使用插件架构，允许您添加和删除服务。正如其他人所说，在使用Tomcat作为其Servlet容器时，您可以将JBoss简化为几乎只是Tomcat服务器的地方。这样做有什么好处？如果你认为你将利用JBoss的其他功能，那么未来的证明。
The thing that attracts many architects to JBoss is its flexibility. It uses a plugin architecture that allows you to add and remove services. As other have said, in uses Tomcat as its Servlet container, so you can literally whittle JBoss down to where it is practically just a Tomcat server. What is the benefit of doing this? Future proofing if you think that you're going to utilize other features of JBoss.
JBoss中的这些服务是预先集成的，旨在提供一致的部署模型，最大限度地减少您编写应用程序逻辑或配置以自行集成它们的工作量。话虽如此，像Spring这样的其他框架在支持统一集成许多流行库和框架的方法方面也做得很好。但由于他们专注于集成第三方库，因此服务之间的互操作性取决于您。由于JBoss正在构建服务和集成平台，因此他们花时间开发（并提供支持）互操作性。
These services in JBoss come pre-integrated and strive to provide a consistent deployment model that minimizes your effort in writing application logic or configuration to integrate them yourself. That being said, other frameworks like Spring also do a great job of supporting a uniform ways of integrating many popular libraries and frameworks. But since they focus on integrating 3rd party libraries, the interoperability between services is up to you. Because JBoss is building the services and the integration platform, they spend time developing (and providing support) for interoperability.
做出选择时要问的一些问题是：
Some questions to ask when making a choice are:
- 你要去吗？使用像EJB这样的标准JavaEE架构组件？
- BTW，EJB可以使用JBoss嵌入式容器在独立的Tomcat中运行，所以如果你只使用EJB，那么你仍然没有使用JBoss
- 您可以通过许多公司（包括我相信的Red Hat）找到对Tomcat的支持。
- 您需要比较成本，因为我认为JBoss的支持并不便宜，但我最近没有查询价格。
- JBoss有一些很棒的集群功能，你可能会通过Red Hat获得良好的集群支持。但是，为了完全公开，我从未与任何其他框架进行任何复杂的聚类以便能够进行比较。
听起来不是一个无耻的插件，但JBoss in Action的第一章是。虽然我们在本章中没有对JBoss与其他应用程序服务器和部署环境进行直接比较，但我们确实讨论了与您的问题相关的架构差异。
Not to sound like a shameless plug, but the first chapter of JBoss in Action is available for free on the Manning website. Though we don't do a direct comparison between JBoss and other applications servers and deployment environments in the chapter, we do talk about the architectural differences a bit, which is relevant to your question.
这篇关于为什么Jboss“更好”？比Tomcat？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！