Decoupling 101 - Why decouple, when not to, progressive decoupling and success stories in decoupling

When does a decoupled architecture create more problems than it solves? Learn the key trade-offs and when to avoid this popular pattern.

#1about 6 minutes

Understanding the basics of decoupled architecture

A decoupled architecture separates the backend content management system from the frontend presentation layer, which communicate via an API.

#2about 5 minutes

Deploying decoupled applications with Platform.sh

Decoupled applications can be deployed using a multi-app configuration in a single repository with separate subdirectories for the frontend and backend.

#3about 6 minutes

Exploring the advantages of decoupling your application

Decoupling enables focused teams, expands the hiring pool to more JavaScript developers, and allows for interchangeable frontends for different devices or audiences.

#4about 5 minutes

Considering the disadvantages and challenges of decoupling

The drawbacks of decoupling include the effort to build an abstract API, increased testing and security overhead, and the risk of team isolation.

#5about 5 minutes

Introducing progressive decoupling as an alternative strategy

Progressive decoupling involves layering a JavaScript framework on top of an existing monolithic frontend, balancing developer needs with content editor workflows.

#6about 4 minutes

Real-world success stories of decoupled architecture

Case studies from a film festival and a SaaS provider demonstrate how decoupling enabled flexibility, faster updates, and better user experiences.

#7about 12 minutes

Deciding when and how to decouple your projects

Key questions are answered regarding project size, migrating existing apps, security overhead, and choosing a frontend framework for a decoupled setup.