I attended WordCamp 2013 (Victoria, BC) this past weekend, my first time at the event. As a WordPress enthusiast, I was looking forward to meeting some like-minded folks, to network, and learn some techie stuff about WordPress.
I really enjoyed the Experts Panel which was a solid un-moderated hour of Q & A. I have an interest in how to build out WordPress network sites that can handle a lot of concurrent read and write traffic. There is a lot of information online about clustering WP, setting up caching servers, database performance tuning, webserver tuning, etc. At the panel I learned that:
- high-volume sites are often hosted using nginx, instead of Apache (does that turn LAMP into LNMP?)
- there is the scalingwp.wordpress.com web site
- object-caching can be performed with memcached and APC
- there is some debate about fastcgi mode WP
- among the core WP developers, Mark Jaquith has online info about scaling WP, even on a budget.
- another core WP developer of note to research scaling WP is Pete Mall
- there are consulting agents out there that can provide scaling skills, who have been there and done that
- HTTPS configuration in WP is not necessarily a slam-dunk. You may have to resort to hacking plugins, as the whole framework is not necessarily united on how to provide HTTPS links
- lots of talk about HyperDB for database scaling
I also enjoyed a session by John Overall on 10+1 essential plugins for WordPress. That is where I learned about the LoginRadius plugin for social identity integration – a neat Canadian SaaS startup! John posted the slide show on the Meetup site I think….
Ben put up a blog post with his notes from the session here.
Related posts
2 Comments
Comments are closed.
Blog Archives
- January 2025
- December 2024
- November 2024
- June 2024
- December 2023
- October 2023
- August 2023
- May 2023
- January 2023
- March 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- June 2021
- May 2021
- April 2021
- August 2020
- July 2020
- June 2020
- July 2019
- June 2019
- February 2018
- January 2018
- August 2017
- July 2017
- June 2017
- January 2017
- December 2016
- September 2016
- June 2016
- October 2014
- January 2014
- June 2013
- April 2013
- January 2013
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- August 2007
Another architecture that was not talked about is using Apache as the webserver and nginx as the reverse proxy. This allows you to configure WordPress as you would normally on your Apache servers and nginx acts as a front end caching mechanism. It will only hit your Apache server if the hit is not cached or there is updated content
Thanks Ben – we’re looking at running WordPress and BuddyPress together, so are researching caching solutions that are optimized for a very dynamic WordPress site.