Glassfish和JBoss 5的真实世界比较？ [英] Real world comparisons of Glassfish and JBoss 5?

问题描述

有没有人在现实世界中都有经验？它们在性能（内存使用率，速度等）方面如何比较？稳定性？

JBoss Seam能够在Glassfish上运行得如何？

解决方案

根据我自己的经验，有很多事情：

1. GlassFish有更好的管理控制台
   （JBoss有三个控制台，每个控制台远非理想）。


2. 在GlassFish上热部署更加可靠


3. JMS在GlassFish上效果更好 - 这适用于GF和JBoss 4.X。
   据我所见，JMS实现在
   JBoss 5.X中进行了大幅修改，所以也许这个声明不再是真的。


4. Web服务在GlassFish上运行得更好，
   我在JBoss上有更多高级配置的问题


5. GlassFish有更多超高端的企业插件，如HA-Database，存储
   数据库中的集群中的用户会话，而不是内存中，因此无论发生什么灾难，完全故障切换都是
   。


6. JBoss更受欢迎，有很多的管理员和开发人员知道它，
   ，因此找到可以在JBoss上开发的人更容易，网络中也有更多的
   资源。有时候这更重要，然后技术优势是
   一种解决方案。


7. GlassFish对开发人员更友善。 GF 3
   上的Web应用程序重新部署大概持续一秒钟 - 为了达到这种速度，JBoss重新部署
   我需要JRebel。此外，如果有人使用NetBeans，
   有许多智能向导，这些智能向导非常有用。


8. GlassFish的未来并不确定，因为收购了SUN由Oracle提供。
   现在甲骨文声称它会支持它，但是谁知道这种支持将如何
   看起来是什么样，它会持续多久。尽管GlassFish是开源的，但几乎没有任何人愿意为他/她自己的需求开发应用程序服务器......
   

从我的角度来看，GF更容易管理，从纯粹的技术角度来看，这是一个更好的解决方案，但它远没有那么受欢迎，而且前景不确定。

I我没有以任何方式与RedHat / JBoss或SUN / GlassFish连接，我的公司（erudis.pl）正在为两台服务器提供支持和开发。

Does anyone have experiences with both in the real world? How do they compare in terms of performance (memory usage, speed, etc)? Stability?

Does JBoss Seam work well on Glassfish?

解决方案

A number of things from my own experience:

1. GlassFish has much better administration console (JBoss has three consoles, each of them far from being ideal).
2. Hot deployment is more reliable on GlassFish
3. JMS works better on GlassFish - this applies to GF vs. JBoss 4.X. As far as I see the JMS implementation was drastically modified in JBoss 5.X, so maybe this claim is no longer true
4. WebServices are working better on GlassFish, I had a number of issues with more advanced configuration on JBoss
5. GlassFish has more super-high-end entrprise add-ons, like HA-Database, that stores user session on a cluster in Database, not in memory, so the full failover is possible, whatever disaster would happen
6. JBoss is more much popular, there are a lot of administrators, developers, who know it, so it is easier to find someone, who can develop on JBoss, there are also more resources in the net. Sometimes this is more important, then technical superiority of one solution over another.
7. GlassFish is friendlier for developers. Redeployment of the web application on GF 3 lasts more or less one second - in oreder to achieve this kind of speed of redeployment for JBoss I need JRebel. In addition, if someone is using NetBeans, there is a number of smart wizards, that are very helpful.
8. The future of GlassFish is not certain because of the acquisition of SUN by Oracle. Right now Oracle claims it will support it, but who knows how this support will look like and how long will it last. Even though GlassFish is open source, hardly anyone is ready to develop application server for his/her own needs...

From my point of view GF is easier to administer, is a better solution from purely technological point of view, but it is far less popular and has uncertain future.

I am not connected in any way with RedHat/JBoss or SUN/GlassFish, my company (erudis.pl) is supporting and developing for both servers.

这篇关于Glassfish和JBoss 5的真实世界比较？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！