部署语言/堆栈 [英] Languages / stacks for deployment
问题描述
我工作的一个相当密集的重写，并给予下列选项进行选择：
I'm working on a rather intensive rewrite and given a choice of the following options:
- JSP / Java的Tomcat上运行
- Apache下运行PHP
- 红宝石（下运行我不知道，ROR？）
我想有几个基本问题了解以上。
A couple of basic questions I would like to know about the above.
速度是一个问题。我们有一个支持的MongoDB数据库，所以我们不应该需要在数据库中的信息等待，但前端必须尽可能快。恒言速度不是问题并没有真正适用于此。如果你在处理一个请求500K +对象，它需要快速。
Speed is a concern. We have a MongoDB backed database, so we shouldn't need to be waiting on the database for information, but the frontend needs to be as fast as possible. The common saying speed isn't a concern doesn't really apply here. If you're processing 500k+ objects in one request it needs to be fast.
可扩展性是另一个问题。假设我们的数据库开花失控。其中（上面的）将提供处理这种最简单的方法？
Scalability is another concern. Suppose our database blossoms out of control. Which (of the above) would provide the easiest method of handling this?
什么是Tomcat的/ JSP和Ruby的共同缺点？平行处理容易做到用PHP或Ruby？
What are common downsides of Tomcat / JSP and Ruby? Is parallel processing easy to do with PHP or Ruby?
的目的不是为了省钱，而是建立一个坚实的，快速的，可扩展的系统，以继续在未来几年的发展。
我会说实话，我是前Java开发人员（的不的JSP）转向PHP开发人员。我对任何事情preference是PHP，但我也是一个大相信使用了合适的工具。该团队足以胜任写这个是什么，我们
I'll be honest, I'm a former Java developer (not JSP) turned PHP developer. My preference for anything is PHP but I also am a big believe in using the right tool for the job. The team is competent enough to write this is anything that we
推荐答案
原因：
- 快速启动
- 没有重新部署/包装
- 直截了当MVC模式
- Groovy的模板/继承意见
- 投递支持依赖关系的JAR文件
发展从来没有得到它的阻碍。任何人都没有学到什么东西，除了放在哪里控制器/模型/视图新。
Development was never hindered by it. No one had to learn anything new besides where to put the controllers / models / views.
这篇关于部署语言/堆栈的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
