Topic: Some advices between choosing framework: ROR or some PHP frameworks


This question may asked so many times. I google about it and got lots of discuss generally. After reading all of them, I go to
a conclusion is choose the framework which your understand to it is the most. But we are willing to lean new language or framrwork to make our app better.
So we need some advices to determine which framework we should go with. So I'm posting here, hope
someone can give some advice from real experience when working with ROR and some PHP Framework.

We are developing a web application. Our application is really a back-end for a system which runs on embedded device. We
are in progress to determine a "good" framework for our need.

Our purposes:
1. Build a business web application.
2. Easy to maintain, update.
3. Easy to scalable.
5. Easy to separate test& live environment.
6. Great performance. (We have like 1000 devices is getting data via our)
7. Easy to deployment.
8. It already has a many components/modules for general purpose such as: ACL, Authentication, Uploading, Picture processing,...   
9. Have a great community behind the framework to support for it.
10. Unit testing.

One thing I notice, code in Ror is very short. To do the same purpose, we can just use some line of code in ROR compare
to PHP. This is better for us. Also we want to use AGILE method in our project. The reason is our product keeps
changing to meet to the need of customer. So I think AGILE method is better than for us than WATERFALL method.

Last edited by vinhnguyen (2011-11-29 14:19:25)

Re: Some advices between choosing framework: ROR or some PHP frameworks

The learning curve of RoR is probably greater the PHP,  but once over the learning curve,  RoR is very productive from a programmer's standpoint.  I can't speak for PHP directly, as I've never used it.  I have used Java/J2EE, and In my opinion,  a RoR programmer can do in one hour what it takes a Java/J2EE programmer 6 to 10 hours.

#2 - answer is yes if everyone on the development team is up to speed on RoR,  on the other hand,  if you ask someone who's never used RoR to maintain some code,  it could be a bit challenging. 

#3 - Scalability is always difficult, regardless of the platform,  there is no magic bullet here,  but there are lot's of very large RoR sites, and lots of ways to deploy RoR.  Past a certain point scalability becomes a problem for the hardware, load balancing schemes, etc.  The ruby interpreter at some point could become a limiting factor,  but only when compared to the Java Virtual Machine,  and even then,  the advantage of the JVM is minor. 

#5 - RoR is fantastic in that regard

#7 - Very easy,  Passenger is very easy,  Capistrano is used a lot , I've never used it.

#8 - Everything you'd ever need is almost certainly available as a RoR Plugin or Gem, or a Ruby gem.

#9 - This forum is pretty good,  there are others, is good.

#10 - yes!

Joe got a job, on the day shift, at the Utility Muffin Research Kitchen, arrogantly twisting the sterile canvas snout of a fully charged icing anointment utensil.