Interesting approach. How do you define the boundary contracts so they stay strict enough for cheaper models without becoming too brittle when the architecture changes?
Through the use of module boundary level contracts and strict checks like dependencies/imports, because that’s where cheaper models would often stray. I think it’s important to keep the checks simple instead of complex coding checks. For example, “accounts is not allowed to import billing”.
Comments
Interesting approach. How do you define the boundary contracts so they stay strict enough for cheaper models without becoming too brittle when the architecture changes?
Through the use of module boundary level contracts and strict checks like dependencies/imports, because that’s where cheaper models would often stray. I think it’s important to keep the checks simple instead of complex coding checks. For example, “accounts is not allowed to import billing”.