Why? Because I was tired of my server randomly going to 100% CPU usage and the only way to revive it was to reboot the server! For a long time, I thought the problem was maybe MongoDB which I was using for isbn.net.in which was running on the same server as the blog. But surprisingly, it was most likely WordPress at fault.
On the same point, it has been quite embarrassing when I get tweets and emails that my blog is down, because of this. Especially embarrassing because I’m supposed to be a developer and I can’t even keep a simple website up? Something had to be done.
When I read patio11’s story of how and why he moved to WPEngine, I found myself nodding and agreeing with him throughout the article, especially the part about WordPress, PHP, Apache being very finicky software.
And I found other people who felt the same way as well. I also liked what I read on the WPEngine company website. And knowing that the guy who blogs at asmartbear.com is the same guy who started the WPEngine company gave me even more confidence in moving to WPEngine.
Since companies and projects are moving on to platforms like AWS (to get rid of hardware headaches) and Heroku (to get rid of deployment, operations and scaling headaches), I didn’t see why I shouldn’t move my personal website to a managed WordPress hosting.
That was when I chalked out a plan to move to WPEngine, and moved it wholesale on a weekend.
I’m glad to be no longer doing the constant monitoring of the server and monitoring of the security and upgrades of wordpress, security of plugins, daily backup, etc. WPEngine does that for me. And it even gives me a staging server if I just want to try out stuff. I can’t wait to try out their upcoming Heroku-style git repository feature.
The most surprising and positive upgrade in moving to WPEngine has been the speed. The blog opens up way way faster than before.
No, they haven’t paid me to write this article, I’m just a satisfied customer (so far).
My old superb theme by Divya Manian (Nimbupani) was beginning to show its software rot – it didn’t have support for widgets or the latest options and so on. So I took the major pieces of that theme and converted the default Twenty Eleven theme to use the same branding. Let me know whether it looks decent.
All in all, I’m happy with the move. And as you may have noticed, my frequency of publishing is starting to pick up, thanks to the having no headaches about the website.