|WP Multisite, AND load-balanced, AND clustered.|
| 1:28 am on Nov 22, 2011 (gmt 0)|
Perhaps the reason there's no good tutorials out there on the blogosphere is because no one has yet achieved this successfully, or at least not without such agony that they've become unwilling to share their experiences.
Anyways, I'm nearly convinced that WordPress is going to be the CMS of choice for a fleet of new sites, and I'm committed to getting it going Multi, ie one installation of wordpress for multiple branded sites, each on their own domain.
Furthermore, it's not going to be acceptable to keep all these eggs in one basket. We predict that traffic is going to be highly fluctual; some days there may be massive deluges of traffic, more than one server can handle. Then other days there may be barely a trickle. These sites need to be load-balanced across multiple Front End Nodes to distribute these sudden loads and provide some failure-tolerance, PLUS we'd like the database to be either 1) clustered 2) federated 3) fault-tolerant with "warm slaves" or some such setup.
How would you do it?
Can WP3.0 - with the "network" option - host multiple sites across multiple, identical, front-end servers? And can it do that in a forward-compatible way, so when there are WP updates, we can actually install them? (ie I don't want to branch the code)
| 1:55 am on Nov 22, 2011 (gmt 0)|
|no one has yet achieved this successfully |
I think these guys might have figured out how to do it: [wordpress.com...] ;-)
Barry Abrahamson, of Wordpress.com fame, chief "Systems Wrangler" for Automattic, posts and speaks about scaling, load balancing and all that. For example....
You might also check out Mark Jaquith's talk
That might lead you to some other resources
| 6:53 am on Nov 23, 2011 (gmt 0)|
Thanks ergophobe! Barry's setup will inspire the basic architecture for this system... though I don't think I'll be needing 1500 servers or a petabyte of storage. yowza.
| 7:06 pm on Nov 23, 2011 (gmt 0)|
Think big dude! Think big!