Question

我撰写了小型网络服务(如内容服务器),以搜寻和满足内容。基本上有2个部分——一个活跃的部分,负责客户认证,并提供内容查询功能。第二部分涉及向认证客户提供固定内容。

在业绩和规模方面,上述服务能成为一个良好的结构?

Just using an application server(tomcat) to do both?
But then I hear apache is better at serving static content having easy configurable options like compressing content. So how about using Tomcat as reverse proxy(using j2ep, noodle..) to apache web servers behind. Tomcat can authenticate and search while the apache servers behind can serve the content.
But Tomcat being the single point of contact, can become a performance bottle neck. So why not use the apache tomcat clustering again to balance load on the entire set up?

基本上看一米,看着一个pache-tomcat集群,其中每一条星座的代理作用都是对背后的一套pache服务器的反向代理。这是否可行? 是否有任何人这样做? 我确实找不到这一点,但找不到任何点。如果可能的话,这一结构是否有潜在的不利条件?

如果是坏的选择,那么这一网络服务的正确途径是什么?

Answer 1

To start with I would use tomcat for both static and non static content. tomcat ( from version 5 AFAIK ) has done well in static content serving as well. But if this is not performing well for you then I suggest that you have Apache httpd as the frontending server and tomcat behind it. I have used mod_jk and the JKMount directive can tells apache what are calls to be forwarded to tomcat. So the stuff that doesnt match the JKMount directive are handled by Apache httpd itself. So your static content can be served by httpd and the non-static requests are directed to tomcat. You can have multiple tomcats depending on the load.

但是,你需要仔细研究固定内容要求如何认证。

为了能够扩大规模,在实际内容和准入之间引入间接程度。如同处理从任何地方获得的内容一样。因此,你可以在地理分布的许多地方复制你的固定内容(或使用CDN)。

希望有助于达成一条轨道。

友情链接