| Hi Skunks, Allow me to disagree with what comrade Saidi mentioned about over-engineering. I think in any enterprise system design a high degree of over-engineering is expected. Personally I would go with start simple but make sure your simple anticipates and expects features that may come up in later releases. About the language of choice, if you want fast turn around times for your development cycles together with ease of use PHP is the way to go. Though I still think it doesn't scale well under increased load. JSPs/Servlets scale very well under load, but are more complex to develop and maintain. Either way you need skills to achieve productivity with both approaches.
Another way to look at it is, you could use a hybrid approach and have PHP for the front end and JSP/Servlets for business logic etc in
the back end. You could then use REST APIs or WebServices to pass messages back and forth within the architecture. A bit of an overkill, but might be the way to go with really high volume systems.
KR, Loki "Excellent people exceed expectations".--- On Tue, 9/1/09, saidimu apale <saidimu@gmail.com> wrote:
From: saidimu apale <saidimu@gmail.com>
Subject: Re: [Skunkworks] PHP vs Servlets/JSP
To: "Skunkworks forum" <skunkworks@lists.my.co.ke>
Date: Tuesday, September 1, 2009, 9:32 AM
From your project description, and at the risk of being buried in an avalanche of skunks criticisms, I'd say: forget the over-engineering, start simple. Scale issues can be fixed
later, if that will ever be necessary. And take advantage of feedback-loops from users by releasing early and often. All this is community wisdom: saidi On Tue, Sep 1, 2009 at 12:18 PM, wesley kirinya <kiriinya2000@yahoo.com> wrote:
Ogure, Dude,
After reading your reasons:
1. It seems like this system will be large. I suggest making sure the Requirements, Architecture and Design are well in place, even before choosing the programming language. Infact with the above in place, choosing the language is simple as all you have to look at are the pros and cons of each.
2. For what it's worth: I recommend servlet/java. Your main issue with this system will be implementing 'Business Logic', unlike systems like Flickr or Twitter. PhP is not typesafe nor is it object oriented.
O_O
--- On Tue, 9/1/09, Rad! <conradakunga@gmail.com> wrote:
From: Rad! <conradakunga@gmail.com>
Subject: Re: [Skunkworks] PHP vs Servlets/JSP
To: "Skunkworks forum" <skunkworks@lists.my.co.ke>, write2ogush@gmail.com
Date: Tuesday, September 1, 2009, 3:20 PM
I don't think the technology is the problem. You will need to answer
- Is the team doing the design good?
- Is the design good (does it cater for concurrency, contention, redundancy, high load etc)
- Is the team doing the development good, organized and able to work as a team?
- Is there a project manager and a team lead?
- In light of the above is the remaining time realistic to do the work?
If the answer to any of these is no then it won't matter what language you use -- you're in trouble either way.
|
-----Inline Attachment Follows-----
|