To ship your Data as a Product, slightly than only a desk or file with out additional enterprise context, is a key precept of the information mesh framework. Contemplating whether or not to ship knowledge as a product by way of an software service (API) or as a pure knowledge construction is a crucial design choice. I’ve beforehand examined this particular problem in part 2 of my three-part series on data mesh. Nevertheless, this submit will talk about the difficulty past the information mesh idea, as a result of I believe it’s so basic. I’ll define the important thing variations after which argue why it’s best to want “Knowledge as a Pure Construction” over “Knowledge as an Software.”
The idea of reworking your knowledge right into a product isn’t new within the realm of knowledge engineering and was used even earlier than the information mesh framework was outlined. Nevertheless, there is a crucial distinction between making a product powered by knowledge and treating the information itself as a product — right here is an effective rationalization for the delicate difference between “Data as a Product” and “Data Product”. On this submit, I give attention to “Knowledge as a Product”, even when I additionally use the time period knowledge product for brevity.