Should you Decouple?

Depending on who you ask, decoupling is either the best way to build break-through user experiences, or nothing short of a pandemic. But what exactly is a decoupled architecture? Why is it such a point of contention in the Drupal community? And how do you figure out if decoupling is right for your product or client?

If you're a product owner or technical lead trying to wrap your head around decoupling, this session is for you. By the end, you'll learn:

• What decoupled architectures are - without spending an hour on the details
• Why it seems like everyone is saying that decoupled architectures are the only viable future
• The dragons of decoupling - where decoupled architectures are difficult or more complex to deal with
• The costs and benefits of decoupling on a project team and budget
• A heuristic for decoupling - a way to quickly evaluate if a project justifies investigation for a decoupled architecture, or if you should just go straight to "full-stack Drupal"