1、DATA MESH BEST PRACTICESAbout me20+years of data and engineering experienceArchitect,builder,speakerFocused on the maturation,and modernization of dataAWS Data HeroFounder of Data FuturesFather of 4(3 boys,1 girl).always building:welding/fabrication/machining/wiring/engineering/programmingWhy do I c
2、are about Data MeshIm a software engineer first,but my superpower is data engineeringMaturing of data engineering system architecture and cultureData MaturityAdopting Data Mesh principles can actually bring Data Engineering to similar Maturity as other well engineered software products.Domain orient
3、edLoosely Coupled via Contracts.Deployed and developed independentlybe better to dataAND data,be betterData MeshComposable data architecture of data products with decentralized ownership and development.https:/ course on data mesh4 principles1.Domain Driven Ownership Organization and Culture -decent
4、ralized ownership Federated DevelopmentData Organization Maturity LevelsCentral-central data team,middle man,a difficult/near impossible jobEmbedded-centrally managed engineers align/embed with product/outcome teamsFederated-central teams develop tools,product/outcome teams execute 2.Data as a Produ
5、ctApply“Data Product Think”.Data is not an afterthought.Data is not what comes out of the tailpipe.Data is a non-functional/functional requirement for all products REQUIRES long term thinking and organizational alignmentData Product ThinkWhat are my analytic requirements?How will i measure the succe
6、ss of this feature/product?What are the requirements of my data,both within my domain/team,and that of my customers?How can I robustly share my data model as fully as possible?Organizational AlignmentReward system,based on MetricsExisting precedence to leveragetech debtinfrastructuredevex3.Self Serv