as you're having a requirement for scalability, php becomes a poor choice (it's generally less (easily) scalable and maintainable than other technologies).
Of course it all depends on how scalable it needs to be, both JEE and ASPx are designed for scaling into the near unlimited requests per second :)
Apart from that, much IMO depends on the available hosting environments, existing knowledge with the customer, and things like that far more than which is "better" as both can be used to create much the same things with similar effort.
Given free choice I'd employ JEE because I'm far more familiar with that than with .NET, but that's not related to technical issues but personal expertise.
That said, JEE hosting tends to be more expensive, with ASP development requiring more expensive tooling.
The tooling is your cost, the hosting that of your customers.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
bandwidth, power, failover, 24/7 monitoring, all costs money. That's a big part of any hosting contract, do you have the expertise to do all that yourself?
Java hosting is generally expensive because it tends to start with the moderately high-end packages which are aimed at businesses that need high performance, storage, and uptime guarantees.
To create those yourself will cost you something similar.
If you're happy with lower specs, hosting a JBoss server and a mySQL (or some other open source dbms) somewhere can be done cheaper, but of course your bandwidth and uptime will suffer.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
no, if you want it cheap you have to sacrifice quality, accept longer and more frequent downtime, less performance, things like that.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
Are you sure that is true? Seems rather unlikely, but if it is, then yes, it's a great drawback.
pritaeas
Posting Expert
5,445 posts since Jul 2006
Reputation Points: 653
Solved Threads: 871
if you use JSP you don't need to change web.xml and typically don't need to restart the server.
Even if you do change web.xml you would just have to redeploy the web application to the server, causing a typical downtime of no more than a few minutes, easy to schedule for night time hours when visitors are unlikely to be inconvenienced.
The same is no doubt true for php as well.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
I have another query.
When i started learning Servlets and JSP, i come to know that whenever we make any changes in our website project files, then we need to restart our server to implement those changes.
Now suppose when my website is accessed by thousands of people each second/minute, at that time if I try to restart server then my website will become inaccessible for some minutes, isn't it a drawback and unhappy users??
Secondly to jwenting comment, it is usual practice that you will have development server and production. Dev is for continuous development bug fixing and production gets major or regular updates where you can notify users about any downtime.
peter_budo
Code tags enforcer
15,432 posts since Dec 2004
Reputation Points: 2,806
Solved Threads: 901
On the original question, I would say ASP.NET.
You can learn one language (let's say C#) and use it all around.
Web Services and WCF...
You can leverage the power of ONE language (let's say C#) and use THE SAME CODE in both Web and non-web stuff.
thines01
Postaholic
2,421 posts since Oct 2009
Reputation Points: 445
Solved Threads: 402
wrong argument. The exact same thing you claim is the reason .NET is the one to go with is also true for Java :)
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
Offering an opinion and a reason for a choice is never wrong.
thines01
Postaholic
2,421 posts since Oct 2009
Reputation Points: 445
Solved Threads: 402
Offering an opinion and a reason for a choice is never wrong.
in this case, the reason is utterly bogus and thus wrong.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
@warlord902 cheap is wrong word in this case. I pay $200 for my hosting and is cheap for me, because I live in UK and service provided by company(VPS, set it as you wish) is fair for me. What would be cheap for you in India?
peter_budo
Code tags enforcer
15,432 posts since Dec 2004
Reputation Points: 2,806
Solved Threads: 901
200$ montly or yearly?
Sorry of course it is yearly.
peter_budo
Code tags enforcer
15,432 posts since Dec 2004
Reputation Points: 2,806
Solved Threads: 901
In php, I can do more design of my website.
I also think PHP would be the best option, It is easy to learn, and allows fast development. It does not have downtime when deploying, I have a dev server and live server, so its just a matter of svn. However the draw back of PHP is that it can get really messy really easily. If speed is your main goal, then I would go for servlets and JSP.
As for using PHP for design on your website, I might have read your post wrong. But you should really sperate the logic from the design. PHP should be at least a 3 tier system, Database -> PHP -> Template, because as I said PHP gets messy, mix php with content and HTML, well its like alphabet soup.
mikulucky
Junior Poster in Training
85 posts since Jan 2012
Reputation Points: 41
Solved Threads: 13