For many companies, their WordPress site is their window to the world and is an important marketing, sales and branding tool that directly impacts their bottom line.
But that site needs TLC and attention in terms of server management, maintenance, updates, etc.; tasks that some might call WebOps, or I've even seen the term WPOps used for this.
So guess who often ends up being tasked with these responsibilities within a company? DevOps.
And guess how much they love that? Not so much.
Being responsible for the health of the company WP site means it takes valuable DevOps resources away from their real job, and also it tends to need their attention at very inconvenient times, like at 2 am or on weekends when they're not by their desks.
And managing WP is not their area of expertise. There's a prevalent perception that WP is "just" a CMS so anyone with some tech chops should be fine "just" managing it on the side. It quickly becomes apparent that dealing with WP needs experience and expertise. Also, "just" spinning up an EC2 instance to host WP tends to not work out well either. It's not so simple.
That's why many of Strattic's champions within companies are DevOps. They often come to Strattic to resolve security or performance issues, but then report that the peace of mind they get from Strattic is a wonderful added value - once the site is on Strattic, it no longer needs constant attention. The static production site on Strattic is stable and resilient, scales effortlessly as needed and can even withstand DDoS attempts, and if there are issues on the original WP site, those can be fixed calmly and patiently rather than in a panic under emergency circumstances since the site is completely decoupled from the production static replica.
Top comments (0)