Until now, we have referred to modules as a strict directory structure containing classes, static files, templates, and extensions. We now must differentiate between upstream or generic modules and our platform implementation modules.
Modules that take care of a specific technical component are now referred to as technical component modules. Technical components themselves are a set of configurations for a certain software running on a system, such as Nginx, Postgres, or LDAP.
There has always been the problem of whether a module is a technical component module or not. There are some patterns that allow you to identify technical component modules:
- Developed upstream with active community
- Open source with README and LICENSE files
- Only manages what is required
- Clearly described entry class with parameters for adoption and reusability
- Allows stacking...