A decoupled website with one CMS.
Decoupled websites, also referred to as “headless browsing” CMS, break apart the front-end and back-end into separate entities. Essentially, when we “decouple,” we are separating the back-end functionality and database from the front-end HTML content. Each entity can have separate code bases and even live on separate servers.
Additionally, you could also have two backend CMS, like Drupal and Magento, that feed out to multiple front-ends. In this scenario, a single content update in one back-end location could update front-end live content in multiple places. For example, changing a product description could simultaneously change the product description on a business-facing website, consumer-facing website, and a mobile application.
By separating the back and front-ends, you are potentially providing an added layer of security. All other things being equal, a customized, a headless CMS is less likely to get hacked. While this isn’t guaranteed, it certainly adds an additional security barrier.
With a decoupled CMS, there’s less of a need to continually upgrade since isolating the back-end code, and not using the supplied front-end code, should provide some hardening.
While using something “out-of-the-box” is the quickest and most economical solution, decoupling is taking something apart and putting it back together again in a different way. This is obviously adding some very fundamental complexities, and might even call for two development teams with separate specialities.
By having a decoupled website, you are less constrained by whatever CMS you are using. CMSs, such as Drupal, provide the core back-end CMS functionalities, and traditionally the front-end functionality by using what’s called “themes.”
Ask our developers to advise you with the better variant.