I have been using a headless Drupal CMS (with Gatsby on the front-end) and leveraging it's "relational" field to connect entities (in place of a DB) and it's been incredibly useful; allowing me to build out an app quite quickly. But I'm curious to know the disadvantages in particular around details like: reduced performance and lack of SQL commands.
However, the advantages as I see them (and have personally experienced):
- A headless CMS will provide a preconfigured API, and some have graphQL.
- It also has a granular security system and GUI for restricting the "authors" who can edit the DB.
- a user friendly GUI interface for creating and editing content instead of a commandline or PHPMyADmin (great for "authors")
- Built in user management (registration, user login, forgot password etc) and Oauth for Facebook and Google.
Someone said that a DB is like an engine and a [monolithic] CMS is like a car, however I see a headless CMS as a car with an engine, a shell, the electrics and transmission (just no fabrication or interior).
For my project, being able to query connected content through CMS in-built graphQL has allowed for a faster development / launch speed.
For anyone who thinks CMSes are only useful for outputting webpages of content and is looking to comment, you're missing the point.
What are the disadvantages or scenarios where this solution is not suitable or has drawbacks?
question from:
https://stackoverflow.com/questions/65650103/what-is-the-disadvantages-of-using-a-headless-api-only-cms-as-a-database 与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
