Modernizing Drupal in the enterprise: A charter for a ... / Arijit Dutta & Mohammed Azharuddin Khan
Modernizing Drupal in the enterprise: A charter for a modern CMS platform
/ Drupal Development /
Arijit Dutta & Mohammed Azharuddin Khan
===
Time: Thursday 20th October 15:55-16:30
Room: Elevate
Track: Drupal Development
===
Headless CMSes such as Contentful or Strapi are making the rounds in VC circles as the next big thing in Enterprise CMS. In this wake, Drupal is an equally powerful and mature contender towards an evolution down this path.
In more recent times, as content increasingly occupies center stage with respect to commerce & data strategies and there is a renewed interest in exploring Drupal internals, development & deployment patterns with mental models that have been commonplace in recent times. As distributed content management such as content meshes emerge, it is inevitable that Drupal as a stack comes under closer technology strategy & architecture scrutiny with integration & composability as key considerations.
Considering this next wave of Drupal deployments will be predominantly modern. What this means is that most of the Drupal deployments of the future will be API first and many of them would be headless. In many way, the headless CMS converges into the realm of CMS as a Platform, albeit with a potentially pluggable content repository provider (under the abstraction of APIs);
The business case for these patterns is very sound. While these drivers exist, the road to modernizing Drupal isn’t exactly the smoothest one. Some of the constraints around Drupal in an enterprise scenarios are:-
1. Difficult to scale modules & subsystems independently of each other
2. Difficult to implement high velocity, high throughput and low latency concerns.
3. Lack of well defined integration architecture
In this session we will provide perspective about the modern software architecture view around Drupal which addresses concerns mentioned above and provide prescriptive advice to overcome these issues via three main things. The key takeaways for audience would be:
1. Externalize API concerns: How to externalize API concerns like security, traffic management, analytics etc to an API Gateway
2. Offload Drupal events into an external event
3. Evolve a platform
===
https://drupalsouth.org/events/drupalsouth-brisbane-2022/schedule/1432
===
Recorded by Tomato Elephant Studio
https://www.tomato-elephant-studio.com/record
/ Drupal Development /
Arijit Dutta & Mohammed Azharuddin Khan
===
Time: Thursday 20th October 15:55-16:30
Room: Elevate
Track: Drupal Development
===
Headless CMSes such as Contentful or Strapi are making the rounds in VC circles as the next big thing in Enterprise CMS. In this wake, Drupal is an equally powerful and mature contender towards an evolution down this path.
In more recent times, as content increasingly occupies center stage with respect to commerce & data strategies and there is a renewed interest in exploring Drupal internals, development & deployment patterns with mental models that have been commonplace in recent times. As distributed content management such as content meshes emerge, it is inevitable that Drupal as a stack comes under closer technology strategy & architecture scrutiny with integration & composability as key considerations.
Considering this next wave of Drupal deployments will be predominantly modern. What this means is that most of the Drupal deployments of the future will be API first and many of them would be headless. In many way, the headless CMS converges into the realm of CMS as a Platform, albeit with a potentially pluggable content repository provider (under the abstraction of APIs);
The business case for these patterns is very sound. While these drivers exist, the road to modernizing Drupal isn’t exactly the smoothest one. Some of the constraints around Drupal in an enterprise scenarios are:-
1. Difficult to scale modules & subsystems independently of each other
2. Difficult to implement high velocity, high throughput and low latency concerns.
3. Lack of well defined integration architecture
In this session we will provide perspective about the modern software architecture view around Drupal which addresses concerns mentioned above and provide prescriptive advice to overcome these issues via three main things. The key takeaways for audience would be:
1. Externalize API concerns: How to externalize API concerns like security, traffic management, analytics etc to an API Gateway
2. Offload Drupal events into an external event
3. Evolve a platform
===
https://drupalsouth.org/events/drupalsouth-brisbane-2022/schedule/1432
===
Recorded by Tomato Elephant Studio
https://www.tomato-elephant-studio.com/record