Pure CMS vs a hybrid
In a refreshing manner, despite the fact that almost anyone else says you just the advantages of united CMS like WP (WordPress), I would like to introduce you something that can inspire and you didn't read elsewhere.
In this post, I take as an example of WP plugins because of WordPress CMS (Content Management System) and its plugins power almost 1/2 of the internet. This CMS had been starting as a blog system (extensible, but for individuals rather than for big companies and SME - Small and medium-sized enterprises). Nowadays, statistically, quantitatively, WP is the most used CMS. This was caused by the fact that many CMSes like WordPress are open-source and it's a preferable choice of designers since they speed up the progress, don't need to learn too much from programming or/and are able to skip the work on the back-end when they already can use one-click installs of WP (or another CMS) core and its plugins, reuse the old code from someone else. But it's not "black and white", there are also disadvantages of cms utilizations also on the side of a client.
Key points (pros of a hybrid, cons of WordPress plugins):
- In benchmarks, complex WP code runs on less than ~1/2 speed of a raw, minimalistically small PHP7 file. WordPress core consists of a collection that includes ~31MB (it can slightly differ) of files. PHP7 isn't either the slowest or fastest programming language but with all the PHP calls for reading on a hard disk (for other WP files), with all that blocking I/O then the choice of a programming language doesn't really matter as most, it isn't the biggest factor that makes a difference. Even, with a slower programming language, any management system or/and a web app altering a WP plugin that is written in a lean/small code has enabled the potential to outperform the robust WordPress code. WordPress team made an amazing job when they created a flexible and multipurpose platform incorporable almost into any linguistic, economic, and technical environment but it added an incredible quantity of code, system checks, a lot of code that you don't really need to run.
- Any added WordPress plugin will be slowing down your site or/and top up computing (hosting) costs when it starts to require better performing servers that can serve more website visitors, but in a hybrid architecture, it works differently. WordPress plugins make your site slower but hybrid apps don't have to.
- WordPress flaws, vulnerabilities are the best known (because WP is most used and open-source code that anyone can read to find some bugs) and something similar is possible to say about WP plugins that can weaken it as a whole. It's not a surprise that websites running on WP are the most common (easier) target for hackers. This is one of the most serious disadvantages of open source cms usage white it can totally ruin many businesses.
- Security updates/upgrades can cause incompatibility. It often happens that after an upgrade, a plugin or theme doesn't work. This is caused by differences in the coding between versions of WP core and its extensions, and themes. This doesn't happen in a case of a hybrid design because there are no dependencies on the CMS.
- The costs are remarkable because very often, the good plugins usually aren't free of charge, the good is often paid (sometimes very expensively) and in the end, all in one together, the development of a hybrid architecture can costs the same or even less than paid CMS plugins.
- Subsequently, on-demand coded apps are well-suit, are capable of meeting your needs, desired behavior, and other expectations. You don't finish having paid for a product which you can't use or makes just a part of the job that you want.
- You can have got both, CMS and external apps (either in PHP or in a different language) that can use the same or separate database.
- The portability of WordPress or any other CMS isn't infinitive thus it limits you, you can get richer and more applications with a hybrid infrastructure.