Things have moved on and we got loads accomplished but…
If you’re one of the 30%+ of the CMS market that makes use of WordPress then I wonder in case you’re starting to view WordPress as the SAP of CMSs. I mean that both in a superb and bad manner. Let’s study what this indicates.
WordPress and SAP – similar?
Owning an oversized chew of a market is often a sign of success and right here, each SAP and WordPress can rightly claim leadership of their domains throughout multiple measures.
SAP started out the existence as a machine that was designed to run your business processes – or as a substitute for your backend administration tactics. It has considering grown to be something on which you may (at a stretch) run most of your digital commercial enterprise. WordPress commenced lifestyles as a blogging platform that morphed into a sort-of CMS. With the proper plugins and extensions, WordPress will be the hub of your digital enterprise in some properly-defined eventualities. Anything media associated as an example is a wonderful candidate.
Both systems are particularly configurable and customizable. In SAP’s case, this has established to be something clients love but which is starting to come below query as clients are searching for easier answers to not unusual issues. The identical is taking place – as a minimum for me – with WordPress. On the one hand, I love that our dev crew can do pretty plenty whatever we want functionally however now, both getting there and preserving the entirety afloat is beginning to become tricky for a few, however now not all the reasons that you may practice to SAP structures.
Once clients understood what SAP can do, many of those identical clients spent, and preserve to spend, vast amounts of IT greenbacks building and refining their SAP landscapes. WordPress is a bit one of a kind. If you’re starting small then you can get away with pretty a great deal the whole lot off the shelf (OTS), both free or industrial (FOTS or COTS.) But the moment you scale, matters take a quantum jump in complexity.
In our panorama, for example, we’ve got some ‘should have’ capability that became, in the beginning, a chunk of FOTS which our developers hacked approximately to a restrained diploma. We’ve gradually delivered or changed a few functionalities for sound commercial reasons but the end result is we have something that is taking an increasing number of sources to preserve in place of innovating. Sound acquainted?
It seems that the code we’re using has now not reached give up of life however it sure as heck wishes refactoring before it sinks us overall performance wise.
Gentle giant or indignant monster?
It would be easy for me to point the finger at WordPress (and its merry band of open supply devotees) to say that open supply may be extremely good however in this example, it’s more just like the Wild West. There are all kinds of crappy code that our devs must push through an increasingly more onerous testing system before releasing it to production. Even while it’s COTS functionality run off a far-flung server that’s no longer on our offerings infrastructure.
But then we have seen some really poor practices from a few well-known plugin clothing which are hitting our servers at a fee that’s now not like a DDoS attack. From an electronic mail I got to these days from our factor man or woman at DevriX, our favored WP guide, build and take a look at partner:
Blacklisting some malicious DDoS calls to our AJAX engine, i.E. Blocking off a few regarded hacky tries hitting non-cached pages
Blocking the subsequent set of user retailers. SEMrush and Moz appear to be extremely demanding, they hit the web page hundreds of instances consistent with hour, and move slowly random pages, i.E. A few are vintage and not in the recent cache pool (as a consequence triggering non-cached requests).
Trying to smooth up a number of the third birthday party calls inside the dashboard to Contextly, CoSchedule, and others that show up inside the Add Post screen in New Relic. They happen too frequently and too frequently, I opened the dashboard yesterday and noticed 18 calls from CoSchedule and Contextly on an unmarried screen in “Add Post” on a web page load which turned into WTF?
Not excellent is it?
And that’s only a half of it. There’s an awful lot greater.
We can resolve a number of those problems by way of in reality killing off the capability that causes issues but then what? In our case, we have some solutions but it begs the query – has that first-rate toolkit of components aka WordPress turns out to be too unwieldy for the time, attempt and money our dev team is spending when we might be innovating towards our subsequent-gen enterprise version?
For its part, WordPress is due to launch an essentially new edition of its CMS beneath the codename Gutenberg which, it thinks, will make life much better for people who want to look WordPress turn out to be a modern CMS. The jury is properly and definitely out on that one. In SAP land we see similar conversations with many customers divided over whether or not a flow to S/4HANA is the path to the future which ought to be adopted now.
My evaluation between SAP and WordPress is incomplete and, some will argue, irrelevant because they satisfy special purposes. I ward off saying – as do SAP customers – that WordPress is embedded and, I’d say imperative to the transport of our business version.
To that volume, I apprehend the torn and angst pushed nature of the decisions colleagues in the enterprise area take after they examine their SAP landscapes.
And – one of the claimed benefits of S4/HANA is decreased database size which interprets to better performance. You can do the same with WordPress but it’s miles a formidable step because it means dumping antique content material. Hmm…