This post is part of our ReadWriteCloud channel, which is dedicated to covering virtualization and cloud computing. The channel is sponsored by Intel and VMware. Read the case study about how Intel Xeon processors and VMware deliver unprecedented reliability in the face of RAM errors.
WordPress has grown by leaps and bounds from its origins as a personal blogging platform. Despite the evidence, though, a lot of folks view WordPress as a CMS that’s exclusively for blogs or small sites. So what if I told you eMusic is moving to WordPress for all its CMS needs? That’s exactly what Scott Taylor talked about this year at WordCamp San Francisco.
Now, eMusic isn’t the world’s biggest site, but it’s nothing to sneeze at either. It serves around 6 million visits per month and “billions of HTTP requests” and millions of page views. The site has 400,000 subscribers. If it can handle eMusic, odds are it can handle your site as well.
But it won’t do it straight out of the box. Taylor, lead PHP developer at eMusic, has been managing eMusic’s transition to WordPress as a CMS platform away from Adobe’s Day CRX. While he’s a big fan of WordPress, he acknowledges that there’s “a process” that you need to follow to get WordPress to scale. And “there will be blood” in the process. Expecting a seamless, smooth transition with no bumps? Not realistic.
Note that not everything is going to WordPress. Taylor says business logic and billing will still “live” in other services, while content, eMusic’s UI, and community will all be served by WordPress.
In his talk, Taylor talks about planning the migration. This includes some basics like making a site map and inventory of content, as well as coming up with a “modular” import process and allowing for “turbulence.” He also notes that you should expect to extend WordPress via plugins, and some you can use off the shelf. For example, Taylor says that the company is using Batcache for (well, duh) caching, bbPress for message boards, BuddyPress for social features, and Akismet for site spam. Well, to avoid site spam.
Taylor also notes that eMusic is making heavy use of Amazon Web Services (AWS), including EC2, S3, RDS and Elastic Load Balancing. eMusic’s streams and downloads come straight from AWS.
The bottom line, though? WordPress does scale, says Taylor. If you have some time, kick back and watch the video of Taylor’s talk. It’s worth the 30 minutes or so, and will definitely give you some good ideas and tips on scaling WordPress. If you’re working with WordPress on a larger site, or thinking about it, let us know what you’re running into with WordPress.
Posted in
and tagged with
- Comment
- Subscribe
Email This- Print This
Tweet This-
Share
Tell us about your road to the cloud and win a MacBook Air with an Intel® Coreâ„¢ 2 Duo Processor. This month’s question:
What workloads are you running under virtualization, and what are you holding back?
WordPress has grown by leaps and bounds from its origins as a personal blogging platform. Despite the evidence, though, a lot of folks view WordPress as a CMS that’s exclusively for blogs or small sites. So what if I told you eMusic is moving to WordPress for all its CMS needs? That’s exactly what Scott Taylor talked about this year at WordCamp San Francisco.nnNow, eMusic isn’t the world’s biggest site, but it’s nothing to sneeze at either. It serves around 6 million visits per month and “billions of HTTP requests” and millions of page views. The site has 400,000 subscribers. If it can handle eMusic, odds are it can handle your site as well.
Please enable JavaScript to view the comments powered by Disqus.
Article source: http://www.readwriteweb.com/cloud/2011/11/how-emusic-scaled-wordpress.php