Data shared as products¶
Data offered for reuse should have a clear owner, purpose, interface, semantic context, supported change path and observable promises.
This principle does not demand that every internal table become a product. Apply product discipline at the boundary where another team is expected to depend on the data.
Join the argument
Agree, challenge or add evidence
Architecture improves when its assumptions are challenged. Say which kind of contribution you're making:
- Challenge I disagree because…
- Evidence We've seen this too…
- Question How would this work when…?
- Alternative Another way to approach this…
- Extension This also implies…
Please keep clients, employers and colleagues unidentifiable. Strong contributions may be quoted and credited on this site. Read the contribution guidelines and the privacy notice.
Comments are provided by giscus and stored on GitHub. Posting requires a GitHub account.