Bob Kepford of Mediacurrent discusses Decoupled Content Management Systems. From their inception, content management systems (CMS) have been built in a monolithic fashion. Lately, however, some CMS practitioners have begun migrating to a decoupled approach. As with any change in approach, there are trade-offs to consider, and a decoupled CMS is not a solution for every use case. However, this approach can help in some situations to improve scale, allow for more specialized team member roles, and to separate data collection from data delivery. In this episode, host Jeff Doolittle spoke with Kepford about what distinguishes a decoupled CMS from a typical, monolithic CMS, what projects and tools are part of the ecosystem, and the trade-offs to consider when choosing an approach to content management.
Show Notes
Related Links
Content Management Systems
Links about Bob
- Guest Twitter: https://twitter.com/kepford
- https://www.mediacurrent.com
- https://decoupleddays.com/
- http://www.theweeklydrop.com/
- https://forthedev.com
- Guest Email: [email protected]
Related Shows and Content
- https://www.se-radio.net/2018/10/se-radio-episode-344-pat-helland-on-web-scale/
- https://www.se-radio.net/2018/12/se-radio-episode-349-gary-rennie-on-phoenix/
Standards-Based Architectures for Content Management
Plone and Content Management
Information Concepts for Content Management
Go Static or Go Home
- https://queue.acm.org/detail.cfm?id=2721993
- https://www.mediacurrent.com
- https://decoupleddays.com/
- http://www.theweeklydrop.com/
- https://forthedev.com
SE Radio theme: “Broken Reality” by Kevin MacLeod (incompetech.com — Licensed under Creative Commons: By Attribution 3.0)
I’d suggest decoupled or distributed systems is usually more of a people problem than a tech one. Monoliths are far easier to reason about and work with until a certain people scale