Data Mesh Newsletter #019
The quick bit…
In the next, and final issue of 2021, scheduled for release on December 21st, I’d like to give this issue back to you, the subscriber. I’ll compile a collection of retrospectives of how you, the subscriber, have evolved your perspective on Data Mesh in 2021 and what your plans for Data Mesh are for 2022 and the challenges you face therein. These will be published in the next issue. Send me your Data Mesh story!
In the last issue, an error was made in attributing the author of the article titled How to identify Data Products? Welcome “Data Product Flow”. The correct author is Paolo Platter of Agile Lab. This was fixed in the online publication. Thank you Agile Lab for pointing this out.
Data Mesh Content Unzipped
Data Domains and Data Products
Author: Piethein Strengholt
The goal described here is to address the practical guidance that are (purposely) not addressed in the Data Mesh principles. The author offers guidance in the form of eighteen principles based on his experience in planning data mesh implementations with customers. Standardization across domains is a theme here. If Data Mesh principles can be thought of as a vacation destination, this is one travel agent’s suggested travel itinerary.
Cimpress Launches the Data Portal as the Center of a New Data Mesh
This press release describes the launch of Cimpress Data Portal which leverages Data Mesh principles and goes on to showcase the benefits therein that are playing an increasingly central role in their portfolio of companies’ business operations.
Data Mesh Meets Universal Authorization
Author: Sanjeev Mohan
Makes the case for universal data authorization to address arguably the most challenging Data Mesh principle of federated computational governance to provide cohesive access across domains that stitches it all altogether.
Bring data analyst to the table
Author: Petr Janda
Petr argues that for data teams, you should look to have a seat at the table instead of being a "data pull monkey", moving from a service model to a product model. Pairing with teams to answer questions instead of being the conduit to data. He also argues that there should be a Chief Analytics Officer in the board room. Perhaps the role of a board level data person needs to go further and be about pairing with executives to 1) achieve data literacy for executives; 2) strongly push the concept of informing decisions with data whenever possible - no more gut decisions; 3) evaluate and shape long term strategic projects; and 4) - as Petr mentions - use active listening in the board room to delve further into the company's strategic decisions and challenges.
Martin Fowler On The Fundamentals Of Software Development | The Engineering Room Ep. 1
Host: Bill Schmarzo, Guest: Martin Fowler
Starting at 18:49, Martin gives Bill a walkthrough of Data Mesh and while doing so provides his classicly concise explanations that have made his published works so popular. A number of other interesting topics discussed around software development here as well.
Upcoming Meetups / Zhamak Stuff
Check back next issue.
Book Nook
If you have any suggestions please send my way.
/Newsletter
If you have questions/comments/concerns/suggestions for future newsletters, please let us know at datacequia@gmail.com.
Special thanks to Datacequia LLC for contributing time and effort to focus on this community and hopefully helping you learn more and give back.