Today, I was working on shifting our object caching backend to Redis at NefisYemekTarifleri. And, it didn’t go well.
As a challenging part of working at the NefisYemekTarifleri.com, first three days Ramadan is the busiest time for us. We get max requests during that period. So, I just wanted to highlight some stats for taking note to myself and sharing some stats about WordPress at scale.
My personal websites (this one and blog.uysalmustafa.com) have been on the multisite for years and finally, I’ve migrated them to separate installation.
One of my favorite series is POI and this quote from the last episode. (It ended over the years ago)
This is the continuation post of my previous post “Advanced Database classes for WordPress“. Please read that post before continue unless you are not familiar with advanced database classes for WP. Well, it’s time to see some configurations and ideas about how Hyper-DB or relevant DB classes might help you to scale.
Let’s talk about WordPress’ advanced database classes. I’m explicitly mentioning HyperDB, but there are other alternatives/forks out there;
Logs are the answer that when something goes wrong. When you work on an enterprise scale, you need a centralized logging mechanism. (You can’t jump one server to other and tail that streams)
We are using old WP-REST-API aka (JSON-REST-API) for years and time to move on WordPress’ core REST API.
I like to use git for my plugins, and deploying them to WordPress.org’s svn from git . I’m using scribu’s scripts and I did small modifications on it – https://github.com/mustafauysal/deploy-from-git
We are using BuddyPress on NYT (largest recipe website of Turkey) and I want to share some ideas and experience about scaling BuddyPress. (We might be second largest BuddyPress user)