Decoupling separates the system that stores the content from how that content is displayed on other systems. The back-end and the front-end(s) are independent of one another. Decoupling comes with many benefits like clean content APIs for mobile applications, reduction in the risk of re-platforming the back-end or redesigning the front-end, and less reliance on Drupal specialists. However, there are also some big potential downsides.
But what if you could get some of the benefits of decoupling your website while minimizing those downsides? What if you could decouple your website without revamping your entire infrastructure? And what if you could begin doing it today?
Enter progressive decoupling, the process of decoupling your website one small piece at a time.
In this webinar, you will learn:
Mateu Aguiló Bosch is a Lead Engineer with extensive experience in API design, Node.js development and contribution, and distributed architectures in the cloud. He loves to be under the sun.
More about MateuNathan Bybee is a technical manager for IBM's AEM Sites development team. He has spent years leading full-stack developers to help bring innovation to ibm.com, from design language to front-end thru back-end development.
Published in: