Gigaspaces公司的大牛Nati Shalom及其同事Geva Perry 的关于在web2.0时代,java在高性能、大容量、高负荷的互联网应用领域所扮演的角色进行了较为理智和深入的思考,在TheServerSide和Artima上也引起了激烈的讨论。由于Nati Shalom及Geva Perry ,都算得上Java的大牛,其所在公司Gigaspaces开发的产品GigaSpaces eXtreme Application Platform (XAP)也是基于Java的高性能平台,因此其观点算得上对Java在互联网时代的定位的反思,相比较而言国内的“我该学习Java还是学习.Net之类的讨论”层次明显得不一样。
讨论的一些相关内容:
Why most large-scale web sites not written in Java
Why most large-scale Web sites are not written in Java [Personal View]
Large-Scale Web Sites and Java
一些Web2.0应用杰出代表的系统架构
我比较赞同Geva Perry 在Large-Scale Web Sites and Java的观点:
my intuition is that the trend for Web apps that are coming from start-ups or large pure web players (as opposed to web apps from airlines, banks, etc.) is definitely towards the LAMP stack. However, Java will still remain strong for a while and especially for Web apps that have to deal with more complex processes in the back-end.
对互联网企业的Web应用而言,强调的是开发、部署、维护的敏捷性,因此我觉得Web层的应用还是采用像RoR、Django、LAMP(CakePHP)的应用架构相对方便,另外在性能调优(例如Cache、页面静态化)方便,像LAMP这样的架构还是较为成熟;在诸如像电子支付这样关注事务完整性、在MVC业务层有复杂的业务逻辑处理(例如交易、结算)的互联网应用领域采用Java架构还是较为恰当的;当然像银行业务、电信系统、电子政务系统这样传统的企业应用领域(Workflow、ESB、Rule Engine、SoA、消息服务等)Java还是会占据较大的优势。
归根结底,采用什么样的语言及架构还是需要根据业务模式的需要来决定。
一些相关的文档,值得一读
http://fishtrain.com/2007/09/26/interview-with-gigaspaces
http://royal.pingdom.com/?p=95
http://royal.pingdom.com/?p=173
http://natishalom.typepad.com/nati_shaloms_blog/2007/10/why-most-scalab.html
http://natishalom.typepad.com/nati_shaloms_blog/2007/10/why-most-large-.html
http://gevaperry.typepad.com/main/2007/10/large-scale-web.html
转载请注明:出家如初,成佛有余 » Why most large-scale web sites not written in Java