opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Add daily email for 2024-10-21

Browse source 
Drupal applications are modular monoliths
This commit is contained in:
Oliver Davies 2024-10-23 00:05:41 +01:00
parent e3ce9e2d78
commit fcc6bb76b7
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
source/_daily_emails/2024-10-21.md Normal file
View file

@ -0,0 +1,28 @@
---
title: Drupal applications are modular monoliths
date: 2024-10-21
permalink: daily/2024/10/21/drupal-applications-are-modular-monoliths
tags:
- software-development
- drupal
- php
cta: d7eol
snippet: |
Drupal applications are modular monoliths.
---
"Modular monolith" has been a popular phrase in the PHP community recently with talks, podcast episodes and courses released on the topic.
The idea is that instead of all the code being in one namespace, like App, it's split into different modules such as for payments or a blog - whatever is relevant and appropriate for that application.
Each module contains its own classes and structure instead of everything being mixed together.
If you want to change something about payments, you go to the payments module and you don't need to worry about anything else.
What's interesting is that this is how I've always built Drupal applications.
Each includes Drupal core and any contributed modules installed via Composer, and a specific directory for application-specific custom modules.
These modules can be separate and standalone or they can interact and have dependencies and sub-modules.
Each has its own routes, services, tests and more, making them easy to organise and maintain compared to having all the custom code in one large monolithic namespace or module.