Scaling Large Scale Web Services

One day I’m going to do a presentation on Scaling Large Scale Web Services with one slide: Use PHP. πŸ˜‰

15 thoughts on “Scaling Large Scale Web Services

  1. PHP isn’t an architecture;

    PHP itself is slow, its how you distribute, store, and retrieve the data that lends itself to being scalable. PHP happens to not bind you into stupid things, like some J2EE or even the Ruby on Rails platform does, but it doesn’t make PHP any better at scalability than Perl, Python, Ruby, C++, or even java (without all the crappy frameworks).

    -Paul

  2. I need to give an updated talk about the Bloglines architecture… the one Mark talks about is pre-memcached and pre-v2 of the distributed filesystem…

  3. So when are you going to get around to doing a presentation on blogging where you start with the concluding slide and work your way back to the title slide? It’s only been, oh, two or three years now since I dared you to do it…

  4. Hah, I nearly bought this and already started to think what to write in regarding that it wasn’t possible with PHP bla bla bla etc πŸ™‚ You got me πŸ˜›

    By the way, your header (the one at the top with the red background) look like it’s cut too short at my 22″ (1680×1050)… πŸ™‚ Just FYI.

  5. That article is weird, it’s really long and half seems to be trying to sell his “Turbo Charged CMS” thing (which I think is just bundled plugins?).

SHARE YOUR THOUGHTS