Are you having issues defining a hierarchy (domain/system/component) or within a specific entity?
What worked well for us was to map out a diagram in Miro (or another comparable diagramming tool) and discuss the split there and only afterwards codify it into the components as that was easier to visualize (and do bulk changes).
In parts were we struggled the components often had too many mixed responsibilities (here splitting into "virtual" components helped) or systems didn't really align with the org structure, but that was mainly feedback for management.
j
jpeach
08/01/2022, 11:31 PM
There is some of that, but also some of “should clickhouse resources be of type
cluster
or
database
?“, “when does it make sense to use a namespace?”
jpeach
08/01/2022, 11:32 PM
I think that your approach would be good for a single team that owns a complicated system