<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Melissa Logan on Medium]]></title>
        <description><![CDATA[Stories by Melissa Logan on Medium]]></description>
        <link>https://medium.com/@melissa_datamesh?source=rss-28b75f9ac4f0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Gsj_2FEENacDspwqodLORg.jpeg</url>
            <title>Stories by Melissa Logan on Medium</title>
            <link>https://medium.com/@melissa_datamesh?source=rss-28b75f9ac4f0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:20:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@melissa_datamesh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Navigating Data Governance: Insights from JP Morgan Chase’s Sarita Baksta]]></title>
            <link>https://medium.com/data-mesh-learning/navigating-data-governance-insights-from-jp-morgan-chases-sarita-baksta-b5e398900e13?source=rss-28b75f9ac4f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5e398900e13</guid>
            <category><![CDATA[data-mesh]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Melissa Logan]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 17:58:22 GMT</pubDate>
            <atom:updated>2024-01-29T17:58:22.771Z</atom:updated>
            <content:encoded><![CDATA[<p>In the complex world of data management, understanding and mastering data governance is essential. Sarita Baksta, a key figure in firm-wide data management at JP Morgan Chase, offers an insightful perspective on the evolving role of data governance. Her career path has encompassed various roles in the financial services industry, ranging from developing mortgage trading applications to overseeing risk and finance technology. In her current role, she focuses on leveraging data responsibly and safely, highlighting the significance of effective data management.</p><p>Drawing on her extensive experience in the financial services industry, this article delves into Sarita’s valuable insights into data mesh data governance.</p><h3>Rethinking Data Governance</h3><p>Traditionally, data governance has been seen as a barrier to innovation, often equated with restriction and control. Sarita challenges this perception, advocating for a transformative approach within the data mesh framework. By adopting a decentralized approach to data governance, she shifts the role of governance from gatekeeper to facilitative force.</p><p>Decentralizing data governance involves distributing decision-making authority to domain teams, granting them more autonomy. This method strikes a balance between central oversight and localized decision making, effectively transforming data governance into a supportive tool rather than an obstacle. In a decentralized framework, domain teams, who are deeply knowledgeable about their specific data sets, play a crucial role in decision making. With their domain-specific knowledge, they provide expertise that central governance teams often lack.</p><p>This shift in governance decentralizes power, moving it away from a single, centralized team. This approach not only places trust in those who are most familiar with the data but also encourages a more responsible and informed approach to data management. By equipping these domain experts with the right tools and clear guidelines, organizations enable a more innovative, agile, and effective use of data.</p><h3>6 Insights into Implementing Effective Data Governance</h3><p>To better understand the practical application of these concepts, here are six critical insights from Sarita on implementing effective data governance.</p><h3>1. Develop Purpose-Built Data Products</h3><p>Focus on creating data products designed for distinct use cases. This ensures each product serves a clear purpose and aligns with specific business needs. By making these products extensible and reusable, you can improve their scalability and encourage the discovery of additional use cases over time.</p><h3>2. Adopt Flexible Governance Principles</h3><p>Embrace a flexible and adaptive approach to data governance. This involves establishing a governance framework that is capable of evolving with your organization’s needs. Encourage an environment where learning from new insights and adapting to challenges is the norm. You won’t know everything up front, so leave room for your approach to evolve as you learn.</p><h3>3. Balance Risk Controls with Innovation</h3><p>Implement risk controls that effectively manage and mitigate potential data risks without stifling innovation. The key is to find a balance: Controls should be robust enough to ensure data safety and compliance, but flexible enough to encourage innovative data use can be challenging. Think of your risk controls as tollgates — they shouldn’t become bottlenecks.</p><h3>4. Establish Standards for Interoperability and Naming</h3><p>Create and uphold standards that facilitate interoperability and effective data discovery. This includes implementing consistent naming conventions and ensuring that data products are compatible across different systems and domains. By setting these standards, you help facilitate efficient data navigation and utilization, making data discovery and integration more effective.</p><h3>5. Ensure Clear Communication Channels</h3><p>Maintain clear and direct communication channels between domain teams and governance experts. This ensures that domain teams have access to necessary guidance and support and promotes a culture of openness and shared knowledge across your organization.</p><h3>6. Approach Data Redistribution Strategically</h3><p>Approach data redistribution with a clear strategy and purpose. You should carefully consider data redistribution efforts to avoid creating unintended data hubs. Effectively managing data redistribution requires you to understand and define the specific roles and purposes of data products within your larger ecosystem. Ensure every act of data redistribution is aligned with a well-defined and intentional goal, reinforcing the strategic use of data within the organization.</p><h3>Conclusion</h3><p>Sarita Baksta’s insights invite a reevaluation of data mesh data governance. This new approach, focusing on enabling and empowering, offers the potential for enhanced data management. By adopting these principles, organizations can navigate the complexities of data governance with greater agility and effectiveness.</p><h3>Learn More about Data Mesh</h3><p>This article covers key insights from Sarita’s extensive experience managing data in the financial industry. To learn more about her approaches for managing data governance, check out this <a href="https://daappod.com/data-mesh-radio/hiatus-rerelease-ep52/">episode</a> of Data Mesh Radio. For more information about how organizations are leveraging data mesh, check out this list of <a href="https://datameshlearning.com/community-resources/user-stories/">user journey stories</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5e398900e13" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-mesh-learning/navigating-data-governance-insights-from-jp-morgan-chases-sarita-baksta-b5e398900e13">Navigating Data Governance: Insights from JP Morgan Chase’s Sarita Baksta</a> was originally published in <a href="https://medium.com/data-mesh-learning">Data Mesh Learning</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Scalable Data Mesh Solutions: Lessons from Disney Streaming]]></title>
            <link>https://medium.com/data-mesh-learning/building-scalable-data-mesh-solutions-lessons-from-disney-streaming-cbe36d2bf8b2?source=rss-28b75f9ac4f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbe36d2bf8b2</guid>
            <category><![CDATA[data-mesh]]></category>
            <dc:creator><![CDATA[Melissa Logan]]></dc:creator>
            <pubDate>Tue, 28 Nov 2023 01:30:01 GMT</pubDate>
            <atom:updated>2023-11-28T01:30:25.260Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0qku4WGJJP-4d-dwBc5dTg.png" /></figure><h3>Introduction</h3><p>In the world of data management, organizations are increasingly shifting toward scalable and efficient solutions. Himateja Madala, the Senior Data Engineering Manager and Head of the Data Mesh Data Platform at Disney Streaming, has been instrumental in redefining Disney’s data systems to follow a data mesh philosophy. This article delves into the insights and key takeaways from Madala’s extensive experience, providing guidance on how organizations can build their own scalable and automated data mesh framework.</p><h3>Insights for Building a Scalable Platform</h3><h3>Choose Between an Existing Data Platform or Your Own</h3><p>When implementing a data mesh strategy, organizations must decide whether to leverage an existing data platform or build their own from scratch. This choice hinges on a careful evaluation of their specific needs, resources, and long-term goals. While an existing data platform can offer immediate access to established tools and technologies, potentially reducing time-to-market and implementation costs, it might also impose limitations that impede the adaptability and scalability crucial for a successful data mesh. On the other hand, building a custom data platform allows organizations to tailor solutions to precise requirements and maintain full control of the architecture. However, this approach can be resource-intensive, demanding substantial investments in terms of time, money, and talent. Ultimately, the decision should align with the organization’s strategic vision, considering factors such as data governance, scalability, and the ability to foster a culture of decentralized data ownership and collaboration within the data mesh framework.</p><h3>Empower Non-Centralized Users</h3><p>Empowering non-centralized users lies at the heart of a successful data mesh implementation. By distributing data ownership and access to various domains and teams, organizations can foster a culture of data democratization and collaboration. Non-centralized users, including data producers and consumers across the organization, gain the ability to manage their own data assets and make data-driven decisions independently. This empowerment is facilitated through clear data ownership boundaries, standardized data access and discovery mechanisms, and a shared understanding of data quality and lineage. By providing these tools and guidelines, data mesh not only reduces the bottleneck of centralized data teams but also ensures that data is effectively utilized by those closest to the business challenges, resulting in more agile and efficient decision-making processes. Essentially, data mesh transforms data into a valuable, decentralized asset that drives innovation and advancement throughout the organization.</p><h3>Embrace a Diversity of Data Products</h3><p>The diversity of data products is a core principle of a data mesh strategy. In a data mesh, data products are the encapsulated, self-serve data assets that cater to specific domain needs. Embracing diversity in these data products means that they can take various forms, such as data APIs, databases, real-time streams, or even machine learning models, tailored to address the needs of individual business units. This approach recognizes that there is no one-size-fits-all solution for data, and encourages innovation and specialization within distinct domains. Data products can be developed to serve various purposes, from analytical insights to real-time decision support, promoting flexibility and autonomy for domain teams. This diversity fosters a dynamic ecosystem where each data product is designed to maximize its value, enabling faster, more efficient, and domain-focused data utilization throughout the organization.</p><h3>Leverage Data Contracts for Quality</h3><p>Leveraging data contracts is critical for ensuring data quality in the implementation of a data mesh. These contracts serve as explicit agreements that define the expectations and specifications for data shared across different domains within an organization. They outline the data’s structure, semantics, and quality standards, ensuring that both data producers and consumers know what to expect. Establishing and adhering to these contracts improves data consistency and reliability while mitigating issues related to data inaccuracies and misinterpretations. Data contracts also facilitate effective data governance, allowing for continuous monitoring and validation of data quality, and providing a structured framework for addressing data quality issues when they arise. These contracts play a crucial role in maintaining high-quality, trustworthy data within the data mesh ecosystem, which is essential for making informed and reliable business decisions.</p><h3>Automate What You Can</h3><p>Through automation, organizations can efficiently ingest, process, and deliver data products to consumers while reducing the risk of errors and minimizing manual intervention. Automation also supports data discovery and cataloging, enabling users to find and access the right data products effortlessly. By automating data quality checks and validation, issues can be identified and resolved proactively, improving data reliability. Automation within the data mesh framework can also enhance scalability, making it easier to adapt to evolving business needs without extensive manual configuration. Automation is a key enabler for achieving the agility, efficiency, and consistency necessary to successfully implement a data mesh, allowing organizations to harness the full potential of their data assets.</p><h3>Enable Trust at Scale</h3><p>Enabling trust at scale within a data mesh is essential for its success, yet it can present challenges. To accomplish this, organizations must implement several key strategies:</p><ol><li>Establish clear and well-defined data contracts and standards, ensuring data consistency, reliability, and adherence to quality benchmarks;</li><li>Employ centralized governance to set these standards and ensure data compliance and security, improving trust in the entire data ecosystem;</li><li>Promote effective metadata management and lineage tracking to provide transparency and traceability, allowing data consumers to have confidence in the data’s origins and transformations;</li><li>Implement data quality monitoring and validation mechanisms to help identify and rectify issues promptly, reinforcing trust in data accuracy; and</li><li>Foster a culture of data ownership and accountability, where domain teams are responsible for their data products, fostering a sense of ownership that further builds trust within the organization.</li></ol><p>With these strategies, trust at scale in a data mesh becomes more than just a technical endeavor. It’s also a cultural and governance transformation that ensures data serves as a reliable and valuable asset driving decision-making and innovation.</p><h3>Consider Owning the Infrastructure</h3><p>There are many factors to consider when deciding whether to own the infrastructure in a data mesh implementation. Owning the infrastructure grants organizations complete control over their data architecture, enabling them to tailor the infrastructure to meet specific performance, security, and compliance requirements. However, this level of control also means taking on the responsibility of managing and maintaining the infrastructure, which can be resource-intensive in terms of time and expertise. Ownership requires a thorough understanding of technology stacks, scalability needs, and data pipeline orchestration, potentially requiring investments in skilled personnel and tools. In addition, owning the infrastructure involves the need to adapt and scale as the organization grows, leading to ongoing capital and operational expenditures. Organizations must carefully weigh the benefits of infrastructure ownership, including customizability and control, against the costs and resource commitments required to ensure a sustainable and efficient data mesh ecosystem.</p><h3>Establish Centralized Governance and Federated Decision-Making</h3><p>Centralized governance provides a framework for setting overarching data policies, standards, and security measures, ensuring data compliance and integrity throughout the organization. It helps maintain consistency and coherence in data management while preventing the emergence of data silos and chaos. On the other hand, federated decision-making empowers domain teams to make decisions about their own data, fostering agility and innovation. It ensures that those closest to the specific business context have the freedom to derive insights and create value from data, without being impeded by central bottlenecks. This dual approach strikes a balance between control and flexibility, allowing an organization to maximize the benefits of data mesh by combining centralized governance for data reliability and compliance with domain-specific decision-making for agility and responsiveness to evolving business needs.</p><h3>Keep Data Within the Mesh</h3><p>Keeping data within the mesh not only reduces data transfer latencies but also enhances data security, privacy, and overall network reliability. Decentralizing data storage and processing improves resilience against hardware failures and cyber threats. It also supports the scalability required for use cases like Internet of Things (IoT) and edge computing, ensuring that as more devices come online, the network stays efficient and responsive. The data mesh architecture also aligns with the increasing focus on data sovereignty, enabling compliance with local regulations while lowering data transmission costs.</p><h3>Learn More about Data Mesh</h3><p>This article covers key insights from Himateja Madala‘s experience building scalable automated access for data mesh at Disney Streaming. To learn more about her approaches for building effective data sharing at scale, check out this<a href="https://daappod.com/data-mesh-radio/data-mesh-platform-at-disney-streaming-himateja-madala/"> episode</a> of Data Mesh Radio. For more information about how organizations are leveraging data mesh, check out this list of<a href="https://datameshlearning.com/community-resources/user-stories/"> user journey stories</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbe36d2bf8b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-mesh-learning/building-scalable-data-mesh-solutions-lessons-from-disney-streaming-cbe36d2bf8b2">Building Scalable Data Mesh Solutions: Lessons from Disney Streaming</a> was originally published in <a href="https://medium.com/data-mesh-learning">Data Mesh Learning</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflections on Building a Data Mesh Platform from Scratch: Insights from Novo Nordisk’s Jyotshna…]]></title>
            <link>https://medium.com/data-mesh-learning/reflections-on-building-a-data-mesh-platform-from-scratch-insights-from-novo-nordisks-jyotshna-9f3509d47080?source=rss-28b75f9ac4f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f3509d47080</guid>
            <category><![CDATA[data-mesh]]></category>
            <dc:creator><![CDATA[Melissa Logan]]></dc:creator>
            <pubDate>Tue, 03 Oct 2023 20:44:59 GMT</pubDate>
            <atom:updated>2023-10-03T20:44:59.671Z</atom:updated>
            <content:encoded><![CDATA[<h3>Reflections on Building a Data Mesh Platform from Scratch: Insights from Novo Nordisk’s Jyotshna Karki</h3><p>In the ever-evolving field of data management, adaptability is key to success. Jyotshna Karki, a data engineer at the pharmaceutical company Novo Nordisk, has seen technology change rapidly over the past seven years. She has helped spearhead Novo Nordisk’s transition from a traditional centralized data lake system to an innovative data mesh approach and has seen the profound impact data mesh has had on the way data is harnessed for business growth.</p><p>When Jyotshna initially joined Novo Nordisk, the company was using a centralized data lake to manage their data. However, with rising consumer and producer demands, Jyotshna’s team realized that a decentralized approach like data mesh offered several benefits: enable domains to independently manage their data products; promote data agility; and allow the central data team to focus on the data mesh platform while aiding less data-proficient domains.</p><p>This article covers 10 powerful insights from Jyotshna’s data mesh journey with Novo Nordisk.</p><h3>10 Insights into Building a Data Mesh</h3><h4>1) Define “Good Enough”</h4><p>Not every solution has to be perfect; it’s more important to ensure that you determine the appropriate point where a solution meets the current needs. Recognize when to prioritize proof of concepts and manual setups for agility, accumulating technical debt to revisit and refine later. Enable steady improvement and avoid wasted effort by pursuing an agile approach to development.</p><h3>2) Leverage Modularity</h3><p>By using modular elements within the architecture you’re leveraging for data mesh, you can set yourself up for efficient development and empower multiple teams to leverage pre-existing solutions efficiently. Focus on the creation of reusable components like pipeline blueprint and prioritize designing for reusability.</p><h3>3) Constantly Assess the Data Product</h3><p>Identify techniques and metrics for monitoring the quality of your data product. Constantly evaluate the architecture to ensure it aligns with business requirements and to identify avenues for ongoing improvements.</p><h3>4) Evolve the Data Product</h3><p>Be open to changing your data product based on shifting requirements. A product-focused mentality encourages evolution and ensures that the architecture you’re using for data mesh remains relevant and valuable.</p><h3>5) Be Curious</h3><p>Foster curiosity in data engineering. Embrace the wealth of innovations available and explore diverse approaches and technologies. An inquisitive mindset drives the discovery of transformative solutions that can significantly impact your data management strategies.</p><h3>6) Balance Centralization and Data Mesh</h3><p>Recognize the balance between a centralized data lake setup and the decentralized principles of a data mesh. You can have happy data producers and consumers within a centralized data lake setup and still have data mesh be the right next step. In the long-run, for some larger organizations, it isn’t efficient to have a centralized data team coordinating all data use cases at scale. Find ways to harmonize data producers and consumers’ needs while avoiding overreliance on a centralized team.</p><h3>7) Address Dependency on Centralized Processing</h3><p>For many domain teams, centralized data processing and storage can be a black box: data goes in, it gets transformed and stored by the central team and then served out. When developing an architecture for leveraging data mesh methodologies, focus on increasing transparency and understanding of the data pipeline. By focusing on transparency, you can empower domain teams by reducing their reliance on external data experts.</p><h3>8) Prioritize Specific Tools</h3><p>When it comes to tool enablement, strive for quality over quantity — concentrate on providing exceptional experiences with widely used tools, rather than trying to support every available tool. With this approach, you can focus on developing high-quality tools that improve the user experience.</p><h3>9) Embrace Data-Driven Development</h3><p>Follow a data-driven approach when moving to data mesh: even if your data is raw to start, you can use it to inform decision-making. With time, your data will become more sophisticated and your approach will evolve into a refined system that aligns with user needs.</p><h3>10) Establish Reliability and Trust</h3><p>Cultivate self-service infrastructure that users can rely upon. Prioritize visibility and transparency in data handling processes to build trust. By providing users with insights into how data is handled, you can provide them with confidence to not just use the platform, but truly rely on its output.</p><h3>Learn More about Data Mesh</h3><p>This article covers key insights from Jyotshna’s extensive experience implementing data mesh at Novo Nordisk. To learn more about her approaches for building effective data sharing at scale, check out this <a href="https://daappod.com/data-mesh-radio/building-novo-nordisk-data-platform-jyotshna-karki/">episode</a> of Data Mesh Radio. For more information about how organizations are leveraging data mesh, check out this list of <a href="https://datameshlearning.com/community-resources/user-stories/">user journey stories</a>.</p><p><em>Originally published at </em><a href="https://datameshlearning.com/reflections-on-building-a-data-mesh-platform-from-scratch-insights-from-novo-nordisks-jyotshna-karki/"><em>Data Mesh Learning</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f3509d47080" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-mesh-learning/reflections-on-building-a-data-mesh-platform-from-scratch-insights-from-novo-nordisks-jyotshna-9f3509d47080">Reflections on Building a Data Mesh Platform from Scratch: Insights from Novo Nordisk’s Jyotshna…</a> was originally published in <a href="https://medium.com/data-mesh-learning">Data Mesh Learning</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Effective Data Sharing at Scale: Insights from Bank of America’s Ramdas Narayanan]]></title>
            <link>https://medium.com/data-mesh-learning/effective-data-sharing-at-scale-insights-from-bank-of-americas-ramdas-narayanan-5d2bdf847bf?source=rss-28b75f9ac4f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d2bdf847bf</guid>
            <category><![CDATA[data-mesh]]></category>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[data-mesh-architecture]]></category>
            <dc:creator><![CDATA[Melissa Logan]]></dc:creator>
            <pubDate>Tue, 25 Jul 2023 23:58:10 GMT</pubDate>
            <atom:updated>2023-07-25T23:58:10.027Z</atom:updated>
            <content:encoded><![CDATA[<p>Ramdas Narayanan, Vice President of Product Management for Data Analytics and Insights at Bank of America, has over a decade of experience building effective data sharing at scale. This article explores some of Ramdas’s insights on implementing data mesh on the operational plane and leveraging data effectively using a data mesh framework.</p><h3>Data Mesh on the Operational Plane</h3><p><a href="https://datameshlearning.com/getting-started/">Implementing data mesh</a> on the operational plane isn’t easy. It requires organizations to build robust data infrastructure, develop and manage data products and services, and execute data-related processes and practices. Additionally, organizations must ensure data quality, enable data access and discovery, and foster a culture of data sharing and transparency. Challenges related to data discovery and the formation of data silos often arise during this process.</p><h3>Improving Data Discovery</h3><p>Data discovery plays a pivotal role in extracting meaningful insights from data. Ramdas emphasizes the importance of educating business professionals on what data is available, as well as what data is not. “That clouded vision of what data is available creates a lot of frustration,” he explains. By providing clarity on what data is available, organizations can prevent stakeholder frustration and empower them to make informed decisions.</p><p>Ramdas suggests that organizations can enhance their data discovery capabilities by hosting information architecture meetings, which provide an opportunity for individuals to share data context and build a stronger understanding of available data. These meetings provide an opportunity for individuals to explore different ways to leverage data and can even spark meaningful conversations across teams. In addition to these meetings, data professionals can contribute to data discovery by enriching dataset metadata to include valuable information and better share context.</p><p>Ramdas emphasizes the need for continuous questioning and assessment of the data flow within the organization. By asking key questions such as “Why are you doing something?”; “What problem are we actually trying to solve?”; and “Do we have the capabilities to solve that challenge or that set of challenges?” organizations can promote effective data utilization. Stakeholders should also assess the overall data flow and processes within the organization by asking questions like “How does the data flow through our systems?”; “Can we push data quality upstream to proactively prevent quality issues?”; and “What guardrails can we put in place to prevent issues?”</p><p>By embracing a proactive approach to data discovery and fostering a culture of continuous assessment, organizations can maximize the value of their data resources.</p><h3>Avoiding Data Silos</h3><p><a href="https://datameshlearning.com/getting-started/common-data-mesh-misconceptions/data-mesh-wont-create-data-siloes/">Data silos pose a common challenge</a> for organizations implementing data mesh. Ramdas cautions against building solutions exclusively for specific problems, as this often leads to the creation of disconnected and fragmented datasets. To avoid data silos, organizations should instead prioritize creating cohesive and reusable datasets. By thoroughly studying data sources to identify valuable data that can be repurposed for other use cases, they can prioritize the data needed to create cohesive datasets.</p><p>Ramdas also suggests involving developers in understanding how business teams will consume and use the data to overcome the challenge of avoiding data silos. By understanding consumption needs, developers can recommend the most suitable approaches for data consumption, whether that’s APIs, web services, or custom batch deliveries.</p><p>By incorporating Ramdas’s insights into their data processes, organizations can enhance data discovery, avoid data silos, and build a scalable data mesh ecosystem.</p><h3>Learn More about Data Mesh</h3><p>This article covers key insights from Ramdas’s extensive experience implementing data mesh at Bank of America. To learn more about his approaches for building effective data sharing at scale, check out <a href="https://daappod.com/data-mesh-radio/adventures-in-data-maturity-ramdas-narayanan/">this episode</a> of Data Mesh Radio and watch videos of other user journeys on the <a href="https://www.youtube.com/playlist?list=PL28WWauQBBu0Ms0sEoaeKriVVI1EJ4iqT">Data Mesh Learning playlist</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d2bdf847bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-mesh-learning/effective-data-sharing-at-scale-insights-from-bank-of-americas-ramdas-narayanan-5d2bdf847bf">Effective Data Sharing at Scale: Insights from Bank of America’s Ramdas Narayanan</a> was originally published in <a href="https://medium.com/data-mesh-learning">Data Mesh Learning</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Future-Proofing Your Data Mesh Architecture]]></title>
            <link>https://medium.com/data-mesh-learning/future-proofing-your-data-mesh-architecture-3a704b423f1?source=rss-28b75f9ac4f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a704b423f1</guid>
            <category><![CDATA[data-mesh]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-mesh-architecture]]></category>
            <category><![CDATA[data-management]]></category>
            <dc:creator><![CDATA[Melissa Logan]]></dc:creator>
            <pubDate>Thu, 08 Jun 2023 16:46:41 GMT</pubDate>
            <atom:updated>2023-06-08T16:46:41.501Z</atom:updated>
            <content:encoded><![CDATA[<p>Our industry’s ecosystem of data management platforms, vendors, technologies, frameworks, services, and practices is constantly evolving to keep pace with client needs.</p><p>We sat down with <a href="https://www.linkedin.com/in/paoloplatter/">Paolo Platter</a>, Co-Founder and CTO of <a href="https://www.agilelab.it/">Agile Lab</a>, to learn more about data mesh and the evolution of data architecture.</p><p>The following is a Q&amp;A discussion inspired by an Agile Lab <a href="https://www.agilelab.it/knowledge-base/technology-abstraction-in-data-mesh">blog article</a>.</p><p><strong>Q&amp;A</strong></p><p><strong>Data Mesh Learning: </strong>Thank you, Paolo, for chatting with us! What are your thoughts on the data mesh architectural framework when it comes to our industry’s changing data management needs?</p><p><strong>Paolo: </strong>Companies that have started the journey toward implementing a data mesh architecture need to seriously consider making their design as future-proof as possible to sustain organizations’ dynamic data strategies.</p><p><strong>Data Mesh Learning:</strong> In your article, you mentioned that, like every significant industrial transformation, a data mesh could–and should–survive at least 10 years. How can companies future-proof their data mesh?</p><p><strong>Paolo:</strong> Data mesh is a strategic and transformative initiative; its architecture must be evolutionary to embrace inevitable change and survive even against a core technological change.</p><p>Embracing the data mesh paradigm is an investment that, if done right, should pay off for years.</p><p><strong>Data Mesh Learning:</strong> In your article, you mention several ways to ensure the longevity of your data mesh architecture: 1) avoiding lock-in, 2) decoupling your data strategy from market risks, 3) avoiding silos, and 4) prioritizing interoperability. Can you walk us through each one?</p><p><strong>Paolo: </strong>First, the entire data mesh paradigm is based on a technology-agnostic approach, so the biggest mistake I see data teams make is when they stake their data mesh implementation on a single holistic data platform or vendor.</p><p>This begs several questions, like:</p><ol><li>How are observability and data contracts exposed if their platform doesn’t offer APIs?</li><li>How is output ports’ polyglotism granted if only topics are supported by the platform?</li><li>Are data products on these platforms atomic and independent deployment units, including infrastructure, data, metadata, and code? and</li><li>If all the domains must use the one-and-only technology and platform, are we decentralizing ownership and providing autonomy?</li></ol><p>You can use one platform or technology as the main backbone — or to achieve a minimum viable product — but I recommend that data teams avoid getting locked into a single platform or vendor.</p><p><strong>Data Mesh Learning: </strong>Can you explain how getting locked in with data platform vendors can affect the longevity of data mesh architectures in the market?</p><p><strong>Paolo:</strong> Your data strategy should be de-correlated to market risks. The goal is to generate business value for your company, and that value should not be affected by external factors. Unfortunately, the recent events around Silicon Valley Bank and other banks have shown us how fragile the technology ecosystem can be.</p><p>Another example of market risk is Hadoop. We had five or six distributions in its early years, but only one has survived today.</p><p>Or do you remember MapR? They had a good customer base with tier-one enterprises. In 2014 they raised $110 million, but by 2019 the company had shut down. The migration for those locked in with their components was a nightmare. In most cases, teams had to rewrite all use cases completely.</p><p>No one can predict the future. So a 10–15 year industrial plan can’t depend on only one or two VC-backed tools. That’s too much risk.</p><p><strong>Data Mesh Learning:</strong> Speaking of tools, you mentioned that teams often find themselves stuck in technology silos.</p><p><strong>Paolo: </strong>Yes, let me paint a picture. Imagine this scenario. You’re a big enterprise that’s planning to implement a data mesh.</p><p>You created the enterprise data warehouse with a specific vendor 10 years ago, embedding business logic with a proprietary PL/SQL. After five years, you started facing issues around scalability, ingestion rates, and time to market.</p><p>Then, you decide to leverage a Hadoop-based data lake platform to address streaming and cost-effective big data use cases at a petabyte scale. While implementing them, you realized the need for the following:</p><ul><li>New tools (data exploration, data quality, data catalog, etc.), but now data is not stored in an RDBMS and is accessible through SQL or JDBC;</li><li>New skills to exploit the computing polyglotism we now have;</li><li>New governance rules and processes because the data lake has different requirements and goals; and</li><li>Duplicating data and business logic from the data warehouse to the data lake due to correlation needs (e.g., customer info joined with credit card transactions).</li></ul><p>At this point, the data lake initiative (with the original aim to unlock new business insights also enabling ML/AI-driven analytics) turned into a completely new data platform with duplicated data, a different tech stack, skills, processes, and policies.</p><p>The original CAPEX investment has tripled, while OPEX costs have multiplied tenfold because you now have two giant silos fighting for budget and use cases, offering the worst-ever user experience for data consumers. This all happened because of technology lock-in.</p><p><strong>Data Mesh Learning:</strong> How do you fight against lock-in?</p><p>Paolo: First, don’t couple teams with technology. Conway’s law says organizations design systems that mirror their own communication structure. In other words, if you have two siloed teams, you will end up with two data silos. So don’t couple teams with technology; connect them with business objectives instead.</p><p>Second, don’t couple tools (for data quality, cataloging, access control, etc.) into a single, all-in-one platform. That increases lock-in and decreases interoperability. The idea of data mesh is to make all data available and correlate it across domains to generate value.</p><p><strong>Data Mesh Learning:</strong> What are the alternatives if a team already has multiple technological silos?</p><p><strong>Paolo</strong>: You have three options:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_bx2oH1WivO3IkqE.png" /></figure><ol><li>Select a(nother) new all-in-one technology platform, plan for a significant migration, and rewrite everything. Maybe this platform now offers lots of native capabilities and proprietary interfaces. Of course, they will speed up the time to market, but there’s a serious risk of creating just another silo because of the lack of interoperability.</li><li>Re-use one of the existing platforms, changing the practice, and reducing the impacts but still locking into a silo with (probably) no capabilities to expand and evolve the technological landscape in the future.</li><li>Create <strong>interoperability standards</strong>. Separate technology and products, use open protocols, and assemble your necessary components. This will allow you to leverage existing technology and introduce new ones in the future. For instance, to develop business logic, you should use only frameworks highly independent from the underlying data storage technology to reduce the overall coupling.</li></ol><p><strong>Data Mesh Learning:</strong> That leads us to your last point: prioritizing interoperability.</p><p><strong>Paolo:</strong> Exactly. Interoperability implies having clear standards:</p><ul><li>For exchanging data products’ data, metadata, formats, output ports’ protocols, observability info, data contracts, and more;</li><li>For open, extensible, and decoupled to any specific single technology; and</li><li>For semantic linking, avoid centralized lock-in on single MDM systems.</li></ul><p><strong>Data Mesh Learning:</strong> Any last advice for organizations implementing data mesh?</p><p><strong>Paolo: </strong>Make it future-proof, and remember:</p><ul><li>Don’t use native facilities (offered by tools) to set interoperability standards. Instead, even if you have just one technology right now, design everything to be able to change it or add one without breaking contracts and standards.</li><li>Decouple storage from computing. You should provide the domains the freedom to choose their preferred (interoperable) compute engine, to process in zero-copy fashion data made available in different data storage technologies.</li><li>Try to be declarative as much as possible, adopting open standards.</li><li>Rely on open and widely adopted protocols to share data across data products via output ports.</li><li>Set your standards for control ports and observability API.</li><li>Don’t couple governance and security processes/policies with specific technologies/data platforms.</li><li>Focus on practice and developer experience more than tools and technologies.</li></ul><p><strong>Data Mesh Learning: </strong>Thank you, Paolo!</p><p><strong>Data Mesh Learning community resources</strong></p><ul><li>Engage with us on <a href="https://datameshlearning.com/join-slack">Slack</a></li><li>Organize a <a href="https://datameshlearning.com/introducing-the-data-mesh-learning-meetup-program-join-your-local-community/">local meetup</a></li><li>Attend an <a href="https://www.meetup.com/data-mesh-learning-meetup-global/">upcoming event</a></li><li>Join an <a href="https://forms.gle/BhXRNSUwihxHthL88">end-user roundtable</a></li><li>Help us <a href="https://docs.google.com/forms/d/e/1FAIpQLSdsCTGB0mBtGgVIREH-segnQyufvAK9bvN6fJ6q5T8zUgUNrg/viewform">showcase</a> data mesh end-user journeys</li><li>Sign up for our <a href="https://datameshlearning.substack.com/">newsletter</a></li><li>Become a <a href="https://datameshlearning.com/community-resources/community-sponsors/">community sponsor</a></li></ul><p>You can follow the conversation on <a href="https://www.linkedin.com/company/data-mesh-learning/">LinkedIn</a> and <a href="https://twitter.com/data_mesh_learn">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a704b423f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-mesh-learning/future-proofing-your-data-mesh-architecture-3a704b423f1">Future-Proofing Your Data Mesh Architecture</a> was originally published in <a href="https://medium.com/data-mesh-learning">Data Mesh Learning</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recap: Data Mesh Days for Life Sciences]]></title>
            <link>https://medium.com/data-mesh-learning/recap-data-mesh-days-for-life-sciences-e7df9e32613?source=rss-28b75f9ac4f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7df9e32613</guid>
            <category><![CDATA[data-mesh-architecture]]></category>
            <category><![CDATA[life-sciences]]></category>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[data-mesh]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Melissa Logan]]></dc:creator>
            <pubDate>Fri, 19 May 2023 17:19:46 GMT</pubDate>
            <atom:updated>2023-05-19T17:19:46.005Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A summary of talks from our first Data Mesh Days event</em></p><p>On Thursday, May 11, we hosted our first-ever Data Mesh Days event with a focus on data mesh implementations and best practices for life sciences. Every domain in life sciences — from drug research to supply chain and commercial teams — relies heavily on data. The data mesh approach empowers domain experts to be accountable for and better leverage their data while sharing it with others to increase innovation and evidence generation, among other benefits.</p><p>Hosted by the Data Mesh Learning community, <a href="https://datameshlearning.com/data-mesh-days/">Data Mesh Days</a> provide a vendor-neutral space where data leaders and practitioners can gather to share and learn about <a href="https://datameshlearning.com/getting-started/#quick-data-mesh-overview">data mesh</a>. Each event will focus on a different industry; this one was Life Sciences, and our next will be Financial Services.</p><p>Our inaugural Data Mesh Day event included five presentations and a breakout session for attendees to meet each other and share learnings. Here’s a quick recap of the presentations, and you can view the full recording of Data Mesh Day <a href="https://www.youtube.com/watch?v=apy8LACHge4&amp;ab_channel=DataMeshLearning">here</a>.</p><p><strong>“Two Years of Data Mesh at Roche Diagnostics”</strong></p><p><a href="https://www.linkedin.com/in/kmaomar/">Omar Khawaja</a> shared how Roche Diagnostics uses data mesh to improve stocking, procurement, and the overall impact for patients and customers. Khawaja stressed the importance of putting at least a little effort into all <a href="https://datameshlearning.com/getting-started/#quick-data-mesh-overview">four data mesh principles</a> and finding a balance–versus focusing on just one or two–to ensure you experience the true benefits of data mesh. Below you can see a snapshot of outcomes of Roche’s two-year journey into data mesh, which includes 50+ operational data products following FAIR principles, average MVP time of 6–8 weeks, 291 releases in a single month (versus one release in two weeks) with coverage for 14+ data domains:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/0*_0beF5ahfY9mMR4F.png" /></figure><p><strong>“The Federated Data Governance Journey”</strong></p><p><a href="https://www.linkedin.com/in/mariana-hebborn-phd-118035117">Mariana Hebborn,</a>Ph.D., led the second talk on data governance. Hebborn is the Healthcare Data Governance Lead at Merck Gruppe. She illustrated the importance of change management — focusing on people and prioritizing conversations and missioning — when implementing any digital or data transformation. She advised data-driven organizations to invest in data governance up front, inspire stakeholder participation, and clearly define processes and procedures to empower project contributors.</p><p><strong>“Data Mesh Strategies in Pharma and Life Science”</strong></p><p><a href="https://www.linkedin.com/in/ammara-gafoor">Ammara Gafoor</a> from Thoughtworks and <a href="https://www.linkedin.com/in/antonioagudodecarlos">Antonio Agudo</a> from Roche Diagnostics led the third discussion, sharing their experiences with data mesh, including common challenges and how to mitigate them. They both agreed that widespread support for data mesh depends on its ability to connect data to value. They recommend working backward from organizational goals to identify high-value analytical use cases, and ultimately, identifying which data products are needed to bring the use cases to life.</p><p><strong>“The Real-World Data (RWD) Store: Accelerating Evidence Generation with Data Mesh”</strong><br>In the fourth session, <a href="https://www.linkedin.com/in/alexandragrebedebarron/">Alexandra</a><a href="https://www.linkedin.com/in/alexandragrebedebarron/">G</a><a href="https://www.linkedin.com/in/alexandragrebedebarron/">rebe de Barron</a> explained how Bayer has fully embraced “data as a product” with its RWD Store, a human- and machine-friendly self-service shop that facilitates real-world evidence generation across the life-long patient pathway. The company adopted a data mesh approach to design data products that serve many users instead of niche tools or applications. As a result, they now prioritize the user experience so that their data products are easy to use, understandable, accessible, secure, interoperable, trustworthy, and valuable. Below, you can see the success of Bayer’s RWD Store by the numbers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*7oNacxzoA3k3NM90.png" /></figure><p><strong>“Implementing Federated Computational Governance with Metadata-driven Automation”</strong><br>For our last speaker session, <a href="https://www.linkedin.com/in/amberhilton/">Amber Hilton</a> and <a href="https://www.linkedin.com/in/%E2%98%81%EF%B8%8F-thinh-ha/">Thinh Ha</a> from Google Cloud explained how embedding metadata quality and governance in developer workflows can enable the data mesh and allow for automation that enables companies to scale. For organizations new to data mesh, Ha recommends first focusing on how you can empower your data teams to deliver value faster and more frequently for your customers, then working backward to identify and adopt specific data mesh principles that will help you reach your goals.</p><p><strong>Insights + Takeaways</strong></p><p>A common theme throughout the day was the need for organizations to inspire and incentivize people to participate and contribute to data mesh. Data mesh is a multi-year journey, so data leaders must explain why data mesh matters to get the buy-in and collaboration needed initially but also keep contributors inspired throughout the process.</p><p>Thank you to all of our <a href="https://datameshlearning.com/community-resources/community-sponsors/">sponsors</a>, the program committee, speakers, and attendees for making the inaugural Data Mesh Days event a valuable experience! To watch the replay, click <a href="https://www.youtube.com/watch?v=apy8LACHge4&amp;ab_channel=DataMeshLearning">here</a>.</p><p><strong>Data Mesh Learning community Resources</strong></p><ul><li>Engage with us on <a href="https://datameshlearning.com/join-slack">Slack</a></li><li>Organize a <a href="https://datameshlearning.com/introducing-the-data-mesh-learning-meetup-program-join-your-local-community/">local meetup</a></li><li>Attend an <a href="https://www.meetup.com/data-mesh-learning-meetup-global/">upcoming event</a></li><li>Join an <a href="https://forms.gle/BhXRNSUwihxHthL88">end-user roundtable</a></li><li>Help us <a href="https://docs.google.com/forms/d/e/1FAIpQLSdsCTGB0mBtGgVIREH-segnQyufvAK9bvN6fJ6q5T8zUgUNrg/viewform">showcase</a> data mesh end-user journeys</li><li>Sign up for our <a href="https://datameshlearning.substack.com/">newsletter</a></li><li>Become a <a href="https://datameshlearning.com/community-resources/community-sponsors/">community sponsor</a></li></ul><p>You can follow the conversation on <a href="https://www.linkedin.com/company/data-mesh-learning/">LinkedIn</a> and <a href="https://twitter.com/data_mesh_learn">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7df9e32613" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-mesh-learning/recap-data-mesh-days-for-life-sciences-e7df9e32613">Recap: Data Mesh Days for Life Sciences</a> was originally published in <a href="https://medium.com/data-mesh-learning">Data Mesh Learning</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>