LesterThomas
commented
1 year ago As part of modelling this, we may want to consider how we model optional dependencies at the same time:
- an optional dependency for a single API would be 0..1
- a required dependency for a single API would be 1..1
- an optional dependency for a list of APIs would be 0..n
- a required dependency for a list of APIs would be 1..n
There is an interesting challenge in how to model a component that can have a variable number of dependencies: For example, an Order Management or Orchestration component will typically integrate to any number of downstream systems. How can a component declare these dependencies? Do we just leave a dependency on a list of components and allow the canvas to populate with 1..n instances?