Demystifying Decoupled Drupal
Session slides can be found here: https://goo.gl/s59kuD
The most exciting development trend we saw in 2016 was the rapid adoption of Drupal 8 and the evolution of the decoupled approach to architecting applications. Decoupling is an advanced solution to breaking up the Drupal monolith by splitting up the work between Drupal and other technologies both on the server and client-side. Drupal 8’s API-first approach provides much more flexibility and allows for the relatively painless implementation of asynchronous elements - even the decoupling of a site’s entire front end presentation layer.
Decoupled Drupal may not be a perfect fit for every project, but it could be the approach you’ve been waiting for to take your application to the next level. Join Corey Wood, Senior Technical Account Manager at Acquia, to discuss the who, what, when, where, why, and how of successfully decoupling Drupal.
What it means for Drupal to be “decoupled”
The benefits of progressively and fully decoupled applications
Integrating with frameworks and playing well with others
The future of front end development in an “API First” world
The performance argument for decoupling: caching, ESI, and more
- Too much of a good thing: caveats and lessons learned