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).
Before anyone takes it *too* seriously, the post is a joke.
If you want serious tips on scaling, talk to folks like Paul and David or check out this these top 10 presentations on scaling. I also really enjoyed this book:
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…
One might argue that HTML is a far more scalable language for a website, as there is far less variability in how it might tax your web server, database, etc.
One *might* want to make that case. I don’t know who, but certainly someone would. Right?
Of course, I think this article does a good job of making that case already:
Are you serious?
Couldn’t agree more.
It hurts to watch the pain of others as they realize these things…
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
Before anyone takes it *too* seriously, the post is a joke.
If you want serious tips on scaling, talk to folks like Paul and David or check out this these top 10 presentations on scaling. I also really enjoyed this book:
http://scalableinternetarchitectures.com/
And Cal’s:
http://www.amazon.com/Building-Scalable-Web-Sites-applications/dp/0596102356
🙂
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…
Does it have anything to do with the dangers of tightly coupling?
http://www.lazycoder.com/weblog/index.php/archives/2007/05/01/the-danger-of-tight-coupling/
… you forgot all the steps.
1. Raise a VC round
2. Buy hundreds of servers
3. Use PHP
4. …….
5. PROFIT!
There’s also a great resource over at http://www.infrastructures.org that talks more about maintaining large systems than it does about performance.
Then again, a system won’t scale if it can’t be maintained and managed. 🙂
Touché!
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…
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.
One might argue that HTML is a far more scalable language for a website, as there is far less variability in how it might tax your web server, database, etc.
One *might* want to make that case. I don’t know who, but certainly someone would. Right?
Of course, I think this article does a good job of making that case already:
http://turbochargedcms.com/2007/04/weathering-heavy-traffic-with-wordpress-and-turbocharged/
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?).
I honestly don’t know how to respond to that, Matt.