启动部署架构 - 在没有 Apache 的情况下运行 Glassfish V3 Prelude
那么我是否疯狂地考虑在 Glassfish V3 Prelude 上发布测试版/生产版？ 由于我的所有内容都是动态的，所以我什至没有考虑在前面设置 apache。 这样做会使设置变得复杂，因为需要 AJP 或 mod_jk 之类的东西，并且不会为我们提供太多功能。
所以部署时会出现三个war文件。 3个JNDI数据源，大约停放了90个连接，扩展到160个PGSQL数据存储......
这三场战争包括一个CMS系统和一个grails应用程序？
我的逻辑是否存在致命缺陷，以至于我不需要将 apache 放在此设置前面？
So am I crazy for considering doing a beta/production release on Glassfish V3 Prelude?
Since all of my content is dynamic, I'm not even thinking of bothering to set up apache in front either. Doing so complicates the setup by requiring something like AJP or mod_jk and will not offer us much in terms of capability.
So there will be three war files on deployment.
3 JNDI data sources with about 90 connections parked, scaling up to 160 to a PGSQL datastore....
The three wars comprise a CMS system and a grails application?
Is my logic fatally flawed that I don't need to put apache in front of this setup?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我有一个在 GlassFish V2 上测试运行的 Grails 应用程序，但我没有找到任何令人信服的理由使用 Apache 进行前端。 我在某处读到（希望我能记住在哪里并引用来源），随着 Tomcat 性能的改进，将 Apache 与 Tomcat 一起使用的理由越来越少。 其要点是增加的性能伴随着足够多的复杂性，因此可能不值得。
是否有特定功能促使您使用 V3 Prelude？
I have a Grails app in test running on GlassFish V2 and I haven't found any compelling reason to frontend with Apache. Somewhere I read (wish I could remember where and cite the source) that with Tomcat's performance improvements there was less and less of a reason to use Apache with Tomcat. The gist of it was the added performance came with just enough added complexity that it may not be worth it.
Is there a specific feature that is pushing you to V3 Prelude?
在 GlassFish/Tomcat/Resin/Jetty/无论什么东西之前使用 Apache 的最大好处是它赋予您的多功能性。 例如，Tomcat 可以取代 Apache，而且效果相对较好。 然而，这意味着所有内容都需要从一个 Tomcat 容器提供，这会引发实例必须执行的大量额外处理，而在图中的 Apache 中则不需要这些处理。 向您的基础设施添加一个简单的基于 PHP 的论坛突然变得有点麻烦，而不是感谢 Apache 的 5 分钟任务。 将 Apache 放在前面的另一个好处是，它使您能够将提供静态内容的负载从容器中移走。 这是我对容器本身提供服务而不涉及 JK/AJP 代理最大的不满。 您的系统会变得更加复杂，并且通用性较差。 但最终，如果它提高了性能，也许这是值得的。
The biggest bonus of using Apache in front of GlassFish/Tomcat/Resin/Jetty/whatever is the versatility it grants you. Tomcat can replace Apache for instance, and that works out relatively well. However, that means everything needs to be served from that one Tomcat container, which is throwing a lot of extra processing that the instance has to do that wouldn't be necessary with Apache in the picture. Adding a simple PHP based forum to your infrastructure suddly becomes a bit of a hassle, rather than a 5 minute task thanks to Apache. Another benefit of putting Apache in front is it allows you the ability to take the load of serving static content away from your container. That's my biggest beef with having a container serve by itself, without an JK/AJP proxies involved. Your system becomes a bit more complex, and a bit less versatile. In the end though, if it increases performance, maybe it's worth it.