Hello, people of the internet, browsing blogs to do with IT and Data. You've found the 2nd part of a data blog which looks at using patterns to form data products. Welcome, dear reader.
In the previous blog, I made some bold claims - promised some patterns to unlock all the goodness, save hundreds of millions, speed everybody up and unify classical physics and quantum mechanics. Ok, not that …
Sounds like I'm selling a silver bullet doesn't it? Actually no. What I'm selling is a butt-load of hard work, arguments and pain. And I'm trying to do this before vendors subvert the meaning of the Data Product and Data Mesh terms to the point where it becomes more meaningless buzzword bullshit.
Standard event driven integration practice is to take data from a system, transform into a middle model and then transform to each destination. Data Autonomy simply says that while we have the data in the middle form, lets save it.
Each business domain must be free to evolve and mature independently as the view of significant business objects evolves. The data governance group with data stewards and SMEs should be responsible for producing domain aligned data product definitions which are then realized into data products. The features of these data products should cover interfaces and persistence for both operational and analytical data.