NingQ.com

mod_proxy vs. mod_jk

新搭建一个开放平台的子项目，配置前端apache时，想用mod_proxy代替mod_jk。google一下两个module的区别，在jboss社区发现了一篇不错的文章。

引用总结如下：

mod_proxy vs. mod_jk

So what to use when? It depends on your topology. In case you already have or need Apache 2.2 functionality you have the choice to choose between mod_proxy and mod_jk. Mod_jk works very well on Apache 2.2, so it all depends on the functionality needed:

mod_proxy

• Pros:
  • No need for a separate module compilation and maintenance. mod_proxy, mod_proxy_http, mod_proxy_ajp and mod_proxy_balancer comes as part of standard Apache 2.2+ distribution
  • Ability to use http https or AJP protocols, even within the same balancer.
• Cons:
  • mod_proxy_ajp does not support large 8K+ packet sizes.(注：mod_jk也并不是无限制，最大可支持64K)
  • Basic load balancer
  • Does not support Domain model clustering

mod_jk

• Pros:
  • Advanced load balancer
  • Advanced node failure detection
  • Support for large AJP packet sizes
• Cons:
  • Need to build and maintain a separate module

Conclusion

My personal suggestion is to use the mod_jk if you can, and if you have the staff to maintain the module binary versions. Mod_proxy is still in active development and misses some of the features from mod_jk. However if there is a need to use the https or a simple load balancing scenario use the mod_proxy.

基于以上描述，其实我们已经能够根据自己的项目需求做出一个选择了。两个module的详细对比分析，大家可以参考原文。

原文来自jboss社区：Comparing mod_proxy and mod_jk