Re: PHP scalability

As a COM/ATL programmer, I may be able to shed some light one this one... =) PHP is just as scalable as ASP; moreso in some ways due to the LACK of COM. See, COM uses RPC. Microsoft's RPC. It's not very good. It's okay, but not very good. So "not very good" that MS programs don't even use it. They have "internal versions" of all of their system services and don't use their "exposed" versions. Ie, things like MSMQ are socket-based...not RPC. Oh, wait...</rant> PHP is more lightweight, and with it's sessions and custom session handlers you can put ANY box behind a hardware load balancer and achieve a "scale out" effect. ASP's a little bit slower, and only supported on MS platforms. That alone limits your "scalability" simply because you have a hardware restriction. If you can live with that, maybe wanting to take advantage of the new AppCenter stuff (the demo I saw he had to run a kill-process on it.....it was, um, just a beta. *giggle insanely*) then you may want to run it. It's a good idea, that AppCenter/DataCenter stuff, but you're running in a new ball game from the old way of doing things. Good idea, not so good implementation. MS technologies just aren't 24/7 capable. Anyone care to comment on why their Hotmail server is NOT WinNT/2k? *grin* So, PHP is cross-platform, can scale-out, is a little faster, has better (IMHO) support, and is NOT Microsoft. True, MS 2k has their new "clustering." It's kinda neat, works almost exactly like a hardware load-balancer with a server farm...but is done in software. They can scale out with it, but they have a "node limit" on it- unlike a hardware balancer. They treat their entire farm as a single address, like a NAT farm, and do "elections" in case their master-server goes down. I've not done any ASP, really, I'm just commenting on your lack of scalability simply restricted to a MS platform/technologies. Running PHP on a MS box works, and should work well. Again, I've not done it. Me, I've just come out of a 2year stint doing COM/ATL in the pursuit of a 24/7 MES manufacturing application. MS is just a pain in the arse, and everything I've said in the previous paragraphs are all lessons learned the hard way. MS just is NOT 24/7, although they're getting closer. Any wonder why they just pust in "application recycling" into their servers? *rofl* It's effectively a cron job to restart your process/services at set intervals. It's, um, exactly the same thing they've been doing for years to bypass a memory problem in their SCM for NT4. If you can live with MS restrictions/technologies, ASP should scale about the same as PHP, except you DO get some AppCenter stuff later which is nice for server farms/clustering. As for MTS, avoid it. Use the new clustering, or get a hardware load balancer. MTS still doesn't have all of the bugs worked out of it yet. They've got another "Business Objects" module coming out, but the name excapes me right now. Again, kinda cool but entirely interpreted and still in Beta. -Szii "There's a reason 62.4% of the world's servers are Apache and not IIS" Oh, and look at the memory requirements for Win2k's "Internet and Security" package...*guffaw* At 03:27 PM 10/26/00 -0400, Duane Douglas wrote: >i'm very well versed in ASP, but not PHP. ASP is very scalable by way of >COM and MTS. i'm wondering if PHP is comparable in scalability. > >how is scalability achieved with PHP? > >tia > >-- >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 >