Drupal core comes with a variety of modules used to build most Drupal sites. The ability to build solutions from reusable components provides agility and speed in building a new experience. Indeed, there are many recipes and starter kits that make building a headless Drupal site easier.īeing modular is a key attribute of a composable architecture. Modules to expose the content via REST APIs using JSON and GraphQL have been available since Drupal 7 and many of these modules are now incorporated into Drupal core. The goal has always been to allow developers to build flexible systems with a modular approach to allow their organizations to quickly adapt to their customers’ needs.ĭrupal was an early adopter of the headless movement. In many ways, as Dries Buytaert points out, Drupal has evolved to be a composable digital experience platform on its own. You may be wondering, if composable is the future, how does Drupal fit in? Drupal has been around for a long time, and during that time, it has continued to evolve. In essence, composable is headless at scale. The architecture is able to adapt to the ever-changing business needs. The front end developers can focus on composing solutions to best meet the end users’ needs. The back end developers can focus on exposing more functionality and platforms. Adding a new channel, platform, or PBC can be done with a faster time to market. Using a composable architecture results in a system that is flexible and agile. There is no one way to build and organize the PBCs, which provides additional flexibility. PBCs allow the data and content to be retrieved from the back-end systems, processed, and returned to the front-end applications in an organized way. To satisfy those responsibilities, the orchestration layer is built using packaged business capabilities (PBCs). The orchestration layer is responsible for integrating with the back-end systems, applying business logic and processes, and providing an interface to provide the data and content to the front-end applications. To achieve those two principles, an orchestration layer is used to separate the front-ends from the back-ends. These two principles are the key to the flexibility provided by a composable architecture. Being back-end agnostic allows a composable architecture to be omni-capable. Being front-end agnostic allows a composable architecture to be omni-channel. Two of the key principles of composable architectures are: composable architectures are front-end agnostic and composable architectures are back-end agnostic. website, mobile app, digital signage) from the back end platforms (e.g. What is Composable Architecture?Ī composable architecture is one that uses a modular approach that effectively separates the digital experience channels (e.g. The speed, agility, and flexibility that composable architectures provide better prepare organizations to adapt to changing technological and consumer trends. Using a composable architecture provides organizations with the ability to add new channels and add or replace digital capabilities quickly. One of the latest trends in the digital experience space is composable architecture. The companies that had built their digital infrastructure with modular and open platforms had a huge advantage over their competitors. Overnight, brick-and-mortar businesses were forced to build or expand their digital footprint. While this has always been true, it has become increasingly evident since the COVID-19 pandemic hit and the disruption to businesses was massive. Businesses need to react quickly to changes and the wants and needs of their customers.
0 Comments
Leave a Reply. |