#57 Using a Knowledge Graph for a Data Marketplace and Data Mesh for Retail - KGC Takeover Interview w/ Olivier Wulveryck and Guest Host Ellie Young

Sign up for Data Mesh Understanding's free roundtable and introduction programs here: https://landing.datameshunderstanding.com/Please Rate and Review us on your podcast app of choice!If you want to be a guest or give feedback (suggestions for topics, comments, etc.), please see hereEpisode list and links to all available episode transcripts here.Provided as a free resource by Data Mesh Understanding / Scott Hirleman. Get in touch with Scott on LinkedIn if you want to chat data mesh.Transcript for this episode (link) provided by Starburst. See their Data Mesh Summit recordings here and their great data mesh resource center here.Ellie's LinkedIn: https://www.linkedin.com/in/sellieyoung/Olivier's LinkedIn: https://www.linkedin.com/in/olivierwulveryck/Knowledge Graph Conference website: https://www.knowledgegraph.tech/Free Ticket Raffle for Knowledge Graph Conference (submissions must be by April 18 at 11:59pm PST): Google FormIn this episode of the Knowledge Graph Conference takeover week, special guest host Ellie Young (Link), founder of Common Action, interviewed Olivier Wulveryck, Senior Consultant and Manager at OCTO Technology.In the first two thirds of the interview, Olivier and Ellie chatted about a lot of concepts specifically around data mesh and then they linked in the concepts around knowledge graph in the last third.For Olivier, a knowledge graph is the map for the data that is available - each data product or node in a data mesh is the representation of the knowledge within the organization. The knowledge graph is the abstraction of that knowledge across the data mesh - a logical representation on top of the data mesh nodes to help people make sense of the data mesh.Currently, Olivier is working with a client sharing their data in a data marketplace. They are working on implementing a knowledge graph on that but not on their internal data. If they are seeing value from applying a knowledge graph externally, they may apply to their internal usage.Olivier shared his view that it's easier to start with a data mesh than a knowledge graph - any first steps with a data mesh will bring you value. It is not the same with knowledge graphs - you have to do more work to get to value with knowledge graphs.Olivier previously worked on the operational side of software engineering. He realized they had lots of data sitting in databases but the data was just a consequence - it was state data, there was no temporal dimension. He wanted...