Re: Scalability and large site issues

The issue of 'large scale' is all relative of course. What 'size' are you thinking about? re: COM. You're correct in pointing out that in ASP, you'd use COM. What is COM? It's normally a Visual C or VB program compiled to a system object. That COM object should be able to be used by other programs on the system, not just the ASP engine. I can't speak directly to the issue of Java, and our Javahead just went out to lunch. In PHP, if you find something's not fast enough, you can write some of your code in C, compile it and call that from the PHP page. Our only experience in doing that is doing 'exec' - I imagine there's a faster way, or you could be adventurous and write it as a PHP module to compile it in to PHP. Maybe even release it for the rest of us, if it's useful. My own experience leads me to the conclusion that the language, while important, most likely won't be the final bottleneck as you expand. A certain nameless flower vendor on the web was, a year ago, using around 80 front end web servers. I guess that means it's scaleable, but there's nothing to stop you, apart from hardware cost, from load balancing requests around to 80 web servers that are running Linux or Unix and PHP rather than ASP. I can tell you your licensing costs will be much less with the Linux solution. Perhaps your development costs will go up some as any inhouse ASP people will have withdrawal symptoms from Visual Interdev, but that's a one time cost... :) As I said, the biggest issue will be hardware/backend. PHP can connect to many databases - running multiple frontend web servers with PHP is fine, as long as the backend database can handle the traffic sent to it. Gary Hall wrote: > Hi > > I need to persuade someone of the superiority of php vs asp vs java. I > appreciate that these sort of questions get asked all the time but I cannot > find an answer to my particular question in the mail archives. > > If an application grows in asp then you write a COM object and port the code > to the COM object (which is compiled and therefore more efficient) to do the > work. > In JSP you would use EJB to build the server side components. > > The above two sets of technologies appear to be tightly integrated into each > other. > > My question is this. If I am writing a PHP application, what enterprise > level server side technology should I be using to make the site more > scalable? Does PHP work well with any other particular technology? or is it > the case that it can link in well with many differing technologies, thats > what makes it so attractive? > > I need to look at a strategy for very large scale sites. Will PHP cope or > will I need to use PHP and something else? If so, what is the something > else? > > Thanks for listening > > Gary > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net -- ========================== Michael Kimsal http://www.tapinternet.com 734-480-9961