Hi all, im going to be starting a pretty big content oriented site soonish.
Currently the site is built in php, and to hit a java flavour would require a rebuild. Im trying to assess which is the best route to approach.
The reason for choosing java would be as i have an expensive semi good cms at my disposal, i have tag libraries to be used etc..
Does any one have any input as to which line i should take. Continue with php which would save replicating the view of the website, and not offer as much longevity + flexibilty. OR switch to java and implement cms + tags etc...
P.s. I know very little about framework tools such as Struts, would that be a feasible option if my cms proved to be too unstable (which it has done before).
You have already been asked to change your display name at least twice. This is your last warning. Please change your display name if you wish to continue posting. We don't ask much of our members. Only to be nice and to abide by our Naming Policy. Help us out here.
Originally posted by Deuce Bigelow: erf.. I had it as underworld, and some one said change it to comply with the policy.
So it said do it so its a real life name, or sounds like one so i did... Ill change it again
We are just trying to keep with an appearnce of professionalism here at the ranch. It's a fun place, hence the moose. But we like to be able to refer to people by real names rather than Alien51, n00b, or Luke Skywalker. Every company has a corporate culture. Ours is simple:
Be nice and follow our Naming Policy.
I appreciate your understanding. Thank you for making the effort to keep Javaranch all that we expect it to be.
My suggestion is if it aint broke, don't fix it. PHP is not a bad technology and it leads the market in domains such as good CMS products.
Continue with php which would save replicating the view of the website, and not offer as much longevity + flexibilty
I'm not sure I follow how PHP doesn't offer longevity + felxibility. I'd assume maintenence might be difficult depending on who built the site, although the same can be said with J2EE projects as I am currently fixing one that is a nightmare due to bad practices and design.
Maybe you could give a little more information on what you expect out of moving this to J2EE? Is there functionallity you need to implement? Will the J2EE version do things the PHP one won't? What is the driving force to make you consider moving to J2EE other than the expensive CMS?
Joined: Sep 22, 2005
These are the factors im trying to weigh up.
FOR Java ======== + CMS to use + Existing tag libs to use + Developers have a bit more experience in java
FOR Php ======= + The current build of the site is PHP, it would save time + money by developing in php.
Another factor to think about is scalability. There is a good chance that down the line this site will have to tie its raw legacy data in with another site which will add a view to the data itself.
The site will be mostly NEWS + Streaming media. Quite a lot of content.
The CMS is currently giving us issues due to it not handling vast amounts of large data objects such as images + video (on a different site).
Thanks for any input/previous experience. [ September 26, 2005: Message edited by: Craig Bull ]
Joined: Sep 22, 2005
I dont know if i made it clear but the site will have a LOT of content + a LOT of users.