"Architecture as Code" (AasC) aims to devise and manage software architecture via a machine readable and version-controlled codebase, fostering a robust understanding, efficient development, and seamless maintenance of complex software architectures
457 introduced time-unit which allows us to record a time in a control-requirement, but we need to be able to also record what it is we need to do in that period of time.
e.g.
"throughput": {
"type": "object",
"properties": {
"expected-message-rate": {
"$ref": "https://calm.finos.org/draft/2024-10/meta/units.json#/defs/time-unit",
"description": "Define the expected message rate that the flow should handle e.g. 1000 per second"
}
},
"required": [
"expected-message-rate"
]
}
Feature Request
Description of Problem:
457 introduced time-unit which allows us to record a time in a control-requirement, but we need to be able to also record what it is we need to do in that period of time.
e.g.
We state how long the thing must take e.g.
But we haven't set what needs to happen in the time, other than by a vague interpretation of the property.
Potential Solutions:
My preference would be for a new specific def per the first option.