architecture-as-code
architecture-as-code copied to clipboard
Pattern Tagging
Description of problem
Patterns help users find architectural solutions to problems they are trying to solve. The solution they are sold for will have certain non-functional requirements that are important to the architecture, these non-functional requirements are known as illities, e.g. durability, scalability security.
It should be possible for users to find patterns that helps solve illity. Additionally, a pattern should conform to an illity by filling the criteria of an illity e.g. to conform to scaleability you must be able to auto scale to 10 times your current compute, autoscaling is triggered when reaching 80% CPU usage.
We would like to propose:
- A pattern has additional taxonomy in the CALM specification to allow for tagging (such as categories or tech stacks).
However, we see the defining usecase the tagging of
illities. - An
illityextension is created that patterns can implement
Tag: @yt-ms, @rocketstack-matt