Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

What is the difference between a decoupled, Headless and RESTful content management system?

+0
−4

By means of content management system architecture,
Is the implementation of decoupling architecture (backend and frontend separation), headless architecture and Representational State Transfer (REST) necessarily related?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+3
−0

Since you ask if a CMS necessarily must be implemented using all three, the answer clearly becomes a theoretical "no" if a CMS can be implemented with anything less than all three, and a practical "no" if a CMS has been implemented with anything less than all three.

REST designs have five constraints:

  • Client–server architecture
  • Statelessness
  • Cacheability
  • Layered system
  • Uniform interface

and optionally

  • Code on demand

Since a content management system clearly can be implemented in a way that requires client-side state (one CMS product that I have to use at work works that way, at least as far as is visible from the user perspective), therefore violating the requirement of statelessness, it is clearly possible to implement a CMS in a way that does not meet the constraints of a REST architecture.

The answer is therefore: there can exist a CMS that does not meet all of the requirements of all the terms you list, as that list includes REST. By your definition of the word "related", they are therefore not "necessarily related".

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »