Hi Jye,

Thanks for the response! The article touches on that topic a bit towards the end, in the Counterpoints → Keeping data formats in sync section… although it doesn’t specifically address the tradeoff that you mention.

Indeed, that tradeoff sometimes needs to be considered, but I’d also add an additional point: often there is not a duplication of interface/data maintenance work (or, at least, there shouldn’t be). By that, I mean that in many cases, teams shouldn’t be striving to ensure that their schemas, interfaces, etc are identical. Rather, each team should store, and expose, its data in the form that makes sense to its domain. It’s the whole “the definition of a product is very different between the shopping and inventory domains” idea.