<?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 Thinh Ha on Medium]]></title>
        <description><![CDATA[Stories by Thinh Ha on Medium]]></description>
        <link>https://medium.com/@thinhha?source=rss-251651952c21------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*pCtmQusmD1MyzvLB.jpg</url>
            <title>Stories by Thinh Ha on Medium</title>
            <link>https://medium.com/@thinhha?source=rss-251651952c21------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:05:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thinhha/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[Accelerating Cloud Migration with Data Mesh Solution Patterns]]></title>
            <link>https://medium.com/google-cloud/accelerating-cloud-migration-with-data-mesh-solution-patterns-a2d502e81208?source=rss-251651952c21------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2d502e81208</guid>
            <category><![CDATA[data-migration]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-mesh]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Thinh Ha]]></dc:creator>
            <pubDate>Mon, 09 May 2022 06:54:41 GMT</pubDate>
            <atom:updated>2022-05-09T23:34:47.919Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Ua02KQnaYAJGbXCb" /><figcaption>Image Credits: <a href="https://unsplash.com/@redzeppelin">Red Zeppelin</a> from <a href="https://unsplash.com/photos/pfiRyJvpyrE">Unsplash</a></figcaption></figure><p>Cloud Computing adoption is rapidly increasing in enterprises. Moving to the Cloud can provide greater flexibility, quicker time-to-market, reduced cost, and improved security and stability. However cloud adoption in the enterprise — in particular, migration of core applications and data — can be slow and fraught with challenges.</p><p>In a recent article <a href="https://towardsdatascience.com/data-mesh-cloud-migration-pattern-fcff598695e4">Data Mesh Cloud Migration Patterns</a> that I collaborated with <a href="https://medium.com/@ericbroda">Eric Broda</a> on, we discussed how enterprises can adopt <a href="https://towardsdatascience.com/data-mesh-solution-and-accelerator-patterns-acffbf6e350">Data Mesh solution patterns</a> such as <a href="https://towardsdatascience.com/data-mesh-pattern-deep-dive-change-data-capture-eb3090178c34">Change Data Capture</a>, <a href="https://towardsdatascience.com/data-mesh-pattern-deep-dive-event-streaming-backbone-99a5bb2a7cbf">Events Streaming</a>, and <a href="https://towardsdatascience.com/data-mesh-pattern-enterprise-data-product-catalog-ba4bf072d7c3">Data Products Catalog</a> to accelerate cloud migration. Eric Broda is a consultant who designs and implements Data Mesh solutions in financial services. Eric has written numerous Data Mesh articles, available at <a href="http://medium.com/@ericbroda">medium.com/@ericbroda</a>.</p><p>The article introduces the notion of a <em>data gravity well</em> to describe a consistent pattern we’ve observed in our clients: <strong>applications and use-cases will be developed closer to where the data they need can be accessed</strong>. Each application exposing valuable data for consumption will naturally draw in additional use-cases and workload. Therefore, a central question you should consider to accelerate your cloud migration is <strong>how are you shifting your data gravity well to the cloud?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d64ksBE3qyBh4bvW" /></figure><p><em>Figure 1. Establishing the Cloud Data Gravity Well (image credits: </em><a href="https://ca.linkedin.com/in/ericbroda">Eric Broda</a>)</p><p>Unbundling on-premises enterprise applications for migration to the cloud is no simple feat. Instead of focusing purely on migrating applications, you can accelerate cloud adoption by unlocking the data produced by these applications and making them readily accessible and available on the cloud.</p><p>The Cloud Migration Data Mesh Solution Pattern achieves this by moving data in near real-time and unobtrusively from an enterprise transactional or analytical system to a secure cloud-native data product. This pattern creates a “live replica” of the original data and does not require application migrations. This offers several tangible and practical benefits:</p><ul><li>It is unobtrusive, requiring zero application changes, thereby alleviating the need to “untangle” the existing application and data spider web.</li><li>Since no application changes are required, this pattern can be deployed very quickly.</li><li>With simpler data migrations, this establishes a cloud “data gravity well” required to accelerate cloud migration.</li><li>As a “live replica”, data is available on the cloud in near real-time providing timely, consistent, and accurate data to newer cloud-native tasks such as AI/ML and advanced analytics.</li><li>With data available on cloud, new applications can be developed quicker and time to market can be dramatically reduced.</li></ul><p>You can read more about this in the article: <a href="https://towardsdatascience.com/data-mesh-cloud-migration-pattern-fcff598695e4">Data Mesh Cloud Migration Patterns</a>. These technical solution patterns combined with the <a href="https://martinfowler.com/articles/data-mesh-principles.html">Data Mesh</a> principles and operating model provide a powerful way to establish a gravity well on the cloud. We believe this can simultaneously accelerate cloud adoption as well as set-up the organization for future scale and agility.</p><p>It is worth noting that building a Data Mesh involves more than adopting technical patterns as it may also require a huge shift in how you think about data culture and data operating model. I have previously discussed cultural and organizational challenges you might encounter when adopting Data Mesh in <a href="https://medium.com/google-cloud/10-reasons-why-you-should-not-adopt-data-mesh-7a0b045ea40f">10 reasons you are not ready to adopt Data Mesh</a>.</p><p>Hopefully this article gives you the necessary insight to kickstart your own Enterprise Data Mesh and accelerate your enterprise’s cloud adoption!</p><p>***</p><p><em>The opinions expressed in this article are mine alone and do not necessarily reflect the views of my clients or Google.</em></p><p><em>The opinions expressed in this article by Eric Broda are his alone and do not necessarily reflect the views of his clients.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2d502e81208" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/accelerating-cloud-migration-with-data-mesh-solution-patterns-a2d502e81208">Accelerating Cloud Migration with Data Mesh Solution Patterns</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recipe for building your first Data Product in a Data Mesh]]></title>
            <link>https://medium.com/google-cloud/recipe-for-building-your-first-data-product-in-a-data-mesh-78b52338ef59?source=rss-251651952c21------2</link>
            <guid isPermaLink="false">https://medium.com/p/78b52338ef59</guid>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-mesh]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Thinh Ha]]></dc:creator>
            <pubDate>Tue, 22 Feb 2022 18:08:34 GMT</pubDate>
            <atom:updated>2022-02-24T07:39:58.132Z</atom:updated>
            <content:encoded><![CDATA[<p>A journey of a thousand miles begins with a single step. For a <a href="https://martinfowler.com/articles/data-mesh-principles.html">Data Mesh</a>, this journey begins with a single <a href="https://www.thoughtworks.com/about-us/events/webinars/core-principles-of-data-mesh/data-as-a-product">Data Product</a>.</p><p>In this article, I will outline a recipe for building your first Data Product. Like all recipes, you are welcomed to adjust it to your context and preferences.</p><p>To bring this article to life, I will also provide an example of what a Data Product architecture looks like on Google Cloud.</p><p>This article assumes that the reader is either the business sponsor for the Data Mesh, or someone who is part of the Data Platform team enabling the Data Mesh.</p><p><strong>1. Find a business case that can be solved with Data Mesh</strong></p><p>First, you need to find a business sponsor who has a specific business opportunity or challenge that cannot be implemented effectively on existing data infrastructure. A few examples are:</p><ul><li>Provide new service offerings through APIs, potentially leveraging predictive analytics</li><li>Build an integrated customer database for improving customer service, marketing, and operations</li><li>Streamlining risk and regulatory reporting</li></ul><p>The ROI for solving this challenge or opportunity needs to justify onboarding a small team of full-time engineers to build and run the solution. Ideally, this business sponsor should 1) have a track record in delivering transformative change programmes and 2) tends to be an early adopter in a <a href="https://en.wikipedia.org/wiki/Technology_adoption_life_cycle">technology adoption lifecycle</a>.</p><p><strong>2. Ensure business readiness and acquire funding</strong></p><p>Second, you need to get buy-in from this business sponsor to own the development of this new Data Product. It is crucial that they understand the goals of a Data Mesh and their role in building this Data Product. Specifically:</p><ul><li>The goal of the Data Mesh is to empower distributed teams to create business value from data. It aims to create a network effect by treating Data as a Product and providing distributed teams with a self-service Data Platform that has embedded governance.</li><li>The business sponsor owns the business requirements for this new Data Product as well as accountability for the end-to-end product development lifecycle.</li><li>The business sponsor will allocate funding for a cross-functional team to deliver the Data Product. This team is responsible for putting together and delivering on a product roadmap to ensure the Data Product captures value for the given business opportunity. They are also responsible for the day-2 operations as well as any ongoing enhancement and maintenance of the product.</li><li>Progress is measured in terms of business outcomes achieved, and funding for the Data Product team can be adjusted upon business review without a change control process.</li></ul><p><strong>3. Prove Data Platform readiness and empower people for success</strong></p><p>Third, ensure your Data Platform has the technical capability to onboard this new Data Product. You need to ensure that any technology or infrastructure services required by the Data Product are approved for use within your organisation.</p><p>The goal is to reduce friction and lower the barrier to entry for adopting these services. As such, there should be clearly documented security guardrails, developer guides, runbooks, and architecture blueprints on how to use these services.</p><p>Crucially, the service should be provided as a self-service capability. This can take the form of an infrastructure-as-code module to deploy a cloud database, or a templated data pipeline that can be easily adopted and extended by distributed teams. The guidance needs to also cover:</p><ul><li>production deployment process following CI/CD best-practices</li><li>how to meet platform-level security and governance guardrails</li><li>how to integrate with the platform’s day-2 operations tooling for logging, monitoring, observability, audit endpoints, etc…</li></ul><p>As a Data Platform team, you are successful when a distributed team can deploy and manage a Data Product without needing to involve you in the process. This proof-point can only be achieved once you’ve onboarded a number of Data Product teams as customers.</p><p>At beginning stages, you may benefit from finding a customer who is willing to co-invest to build the Data Platform components they need. Your priority as a Data Platform team is to develop the capabilities for this Data Product in a way that will be reusable by other customers of the platform, while your customer’s priority is to ensure the platform is fit-for-purpose for a live Data Product application.</p><p>You may also benefit from embedding Data Engineers from the Data Platform team into the business domain team. In this engagement model, the business domain team owns the product backlog, while the Data Engineers provide the technical expertise to deliver on the backlog <strong>as part of the same team</strong>. At the end of the engagement, the Data Engineers can choose to stay in the product team or return to the Data Platform team to start repackaging what they developed for reuse by other Data Platform customers.</p><p>It is worth nothing that the Data Platform itself is an internal product, and in the words of Matthew Skelton from Teams Topologies fame, should be a <a href="https://twitter.com/matthewpskelton/status/1305630151867330571?lang=ca">“curated experience for engineers”</a>. The Data Platform’s goals of empowerment, lowering technical barriers, and minimising collective technical debt are all in service of the communities using it, such as the Data Product teams, and therefore require constant feedback from its customers and refinement to achieve its purpose.</p><p><strong>4. Tell your success story</strong></p><p>Developing a Data Product is an incremental process, as such you will benefit from setting intermediate milestones for regularly reviewing progress and the business impact achieved with your sponsors. This is also your opportunity to celebrate any successes and share your success stories with the rest of the organisation in order to attract additional customers to the Data Mesh.</p><p><strong>5. Rinse and repeat</strong></p><p>With every Data Product, you should aim to shorten the time-to-value for the next sets of Data Products on-boarded onto the Data Platform. The value of the overall Data Mesh should be at least proportional to the combined value of your Data Products. With a larger number of Data Products, the value of the Data Mesh should grow exponentially due to the network effect allowing Data Products to build on top of each other.</p><p>As you can guess, adopting Data Mesh may require a huge shift in how you think about Data Culture and Data Operating Model. I have previously discussed cultural and organisational challenges you might encounter when adopting Data Mesh in <a href="https://medium.com/google-cloud/10-reasons-why-you-should-not-adopt-data-mesh-7a0b045ea40f">10 reasons you are not ready to adopt Data Mesh</a>. The goal of this article is to balance out the message from the previous article with a key message: <strong>you can start small and evolve into the full Data Mesh, one Data Product at a time!</strong></p><p><strong>Example Data Product Architecture on Google Cloud</strong></p><p><a href="https://cloud.google.com/customers#/products=Data_Analytics,Databases">Many organisations</a> have built successful Data Products on Google Cloud, leveraging our comprehensive suite of serverless and integrated data services such as:</p><ul><li><a href="https://cloud.google.com/bigquery">BigQuery</a> for serverless data warehousing</li><li><a href="https://cloud.google.com/dataflow">Dataflow</a> for unified batch and streaming data processing</li><li><a href="https://cloud.google.com/dataproc">Dataproc</a> for <a href="https://cloud.google.com/dataproc-serverless/docs">serverless Spark</a> and for running open-source Data Analytics applications</li><li><a href="https://cloud.google.com/looker">Looker</a> for embedded analytics and visualisation</li><li><a href="https://cloud.google.com/vertex-ai">Vertex AI</a> for end-to-end MLOps</li><li><a href="https://cloud.google.com/composer">Cloud Composer</a> for a managed <a href="https://airflow.apache.org/">Apache Airflow</a> workflow orchestration service</li><li><a href="https://cloud.google.com/spanner">Cloud Spanner</a> for a serverless and battle-hardened relational database service</li></ul><p>The diagram below illustrates a typical Data Products architecture on Google Cloud. The diagram was taken from <a href="https://cloud.google.com/blog/topics/developers-practitioners/introducing-google-cloud-architecture-diagramming-tool?utm_source=twitter&amp;utm_medium=unpaidsoc&amp;utm_campaign=CDR_pve_gcp__4words_&amp;utm_content=-">Google Cloud Architecture Diagramming Tool</a>, courtesy of <a href="https://twitter.com/pvergadia?lang=en">@pvergadia</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HZUAvcag4VTWkEpYYggASQ.png" /></figure><p>In this architecture, each Google Cloud tenant has their own <a href="https://cloud.google.com/resource-manager/docs/creating-managing-projects">project(s)</a> where they can manage the end-to-end lifecycle of their Data Products, leveraging deployment templates and guardrails provided by the Data Platform team. Most of the services are serverless so there is minimal infrastructure to manage, allowing Data Product teams to focus on generating value from their data. To ensure global interoperability and governance, Data Platform tenants can additionally benefit from the following horizontally integrated services across the Google Cloud data stack:</p><ul><li><a href="https://cloud.google.com/analytics-hub?utm_source=youtube&amp;utm_medium=unpaidsoc&amp;utm_campaign=CDR_ali_gcp_h8_xcbtyttu_#section-3">Analytics Hub</a> for zero-copy data sharing with BigQuery</li><li><a href="https://cloud.google.com/dataplex">Dataplex</a> for unified governance across Data Lakes and Data Warehouse environments</li><li><a href="https://cloud.google.com/iam">Cloud IAM</a> for unified access management across all Google Cloud services</li><li><a href="https://cloud.google.com/products/operations">Cloud Operations Suite</a> for integrated logging and monitoring</li><li><a href="https://cloud.google.com/asset-inventory">Cloud Asset Inventory</a> for auditing assets across all projects and services</li></ul><p>For more information on how to build a Data Mesh on Google Cloud, please see the new <a href="https://cloud.google.com/blog/products/data-analytics/build-a-data-mesh-on-google-cloud-with-dataplex-now-generally-available">Google Cloud Data Mesh Whitepaper</a> published as part of the Dataplex GA launch.</p><p><em>Hope you found the article helpful. Is it missing something? Let me know what you think by reaching out to me on Twitter at </em><a href="https://twitter.com/thinh_ha"><em>@thinh_ha</em></a><em> or on </em><a href="https://www.linkedin.com/in/%E2%98%81%EF%B8%8F-thinh-ha-58945969/"><em>LinkedIn</em></a><em>.</em></p><p><em>Special thanks for my colleagues Akhilesh Singh, Anant Vikram, andRubén Fernández who helped review this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78b52338ef59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/recipe-for-building-your-first-data-product-in-a-data-mesh-78b52338ef59">Recipe for building your first Data Product in a Data Mesh</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 reasons why you are not ready to adopt data mesh]]></title>
            <link>https://medium.com/google-cloud/10-reasons-why-you-should-not-adopt-data-mesh-7a0b045ea40f?source=rss-251651952c21------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a0b045ea40f</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-mesh]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[data-architecture]]></category>
            <dc:creator><![CDATA[Thinh Ha]]></dc:creator>
            <pubDate>Mon, 03 Jan 2022 09:33:15 GMT</pubDate>
            <atom:updated>2022-05-02T17:09:18.322Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T0Cl1mihqcYnWfNk6Lwi7w.jpeg" /><figcaption>Image Credits: <a href="https://unsplash.com/@fakurian">Fakurian Design</a> (<a href="https://unsplash.com/photos/E8Ufcyxz514">image source</a>)</figcaption></figure><p><em>Disclosure: </em>I am employed by Google Cloud Professional Services, however the opinions expressed here are mine alone and do not reflect the views of my employer.</p><p>There is a lot of excitement and scepticism at the moment about Data Mesh. Much has already been written about <a href="https://martinfowler.com/articles/data-mesh-principles.html"><em>what</em> a Data Mesh <em>is</em></a>, so I will not recap them here. In this article, I want to provide a view on why you should <em>not</em> adopt Data Mesh as I believe this perspective is missing from existing literature.</p><p>To be clear, I did not write this article to dismiss Data Mesh. I have personally found the concepts useful in my work advising GCP customers on large-scale data transformation programmes. The goal of this article is to encourage constructive conversations around Data Mesh adoption by describing where Data Mesh may <em>not</em> be the right solution.</p><p>With that, let’s get started:</p><h3>1. You are not operating at a scale where decentralisation makes sense</h3><p>Data Mesh is fundamentally about eliminating central bottlenecks in delivering value from data.</p><p>However, moving towards a completely decentralised model risks creating data silos, unnecessary duplication of effort, and may require bridging a much larger data analytic and engineering skill gap than what can be justifiably achieved by decentralised teams alone.</p><p>Therefore, effective decentralisation still requires centralised coordination to align, enable, and support the decentralised data teams.</p><p>This coordination overhead may not be justifiable for small to medium sized organisations, e.g. a 100 people organisation with 2–3 FTEs focusing on data and analytics. Instead, analytic needs across the organisation may be served more quickly and efficiently by a small and centralised data team.</p><p>On the other hand, a 100,000 people organisation spread across multiple geographical jurisdictions or legal entities will inevitably reach scaling bottlenecks with a single centralised data team. In these organisations, decentralisation will naturally emerge, and they most likely already have central business functions tasked with coordination and alignment across distributed teams. In which case, Data Mesh may be a suitable framework to structure this coordination and alignment effort.</p><h3>2. You do not have a strong business-case for how adopting Data Mesh will deliver business value for individual business units</h3><p>Borrowing ideas from DevOps, Data Mesh proposes federating ownership for generating value from data into individual product-oriented teams in order to enable faster value-creation and learning cycles. Each iteration cycle must therefore be guided by a clear and rapid feedback-loop as to what value each data team is generating for their customers.</p><p>Federating ownership often makes sense because business value can be better defined, prioritised, and iterated on by the business unit with the requirement.</p><p>However, taking on ownership over data analytic and engineering require investment that may not be justifiable for some business units without a strong business-case.</p><p>Therefore, it is unlikely that you will be able to fully realise the operating model described by Data Mesh from the beginning. Instead, you should focus on rapidly proving the value from adopting Data Mesh over many short iteration cycles with a few early adopters and collaborate with the remaining business units to build the business-case for adopting this change more widely.</p><h3>3. You treat Data Mesh as a technical solution with a fixed target rather than an operating model that continuously evolves over time</h3><p>I interpret the core goal of Data Mesh is to enable your organisation to leverage data to more effectively adapt to changes and more rapidly meet customer needs. As such, Data Mesh is a means to an end, not an end in itself.</p><p>Furthermore, there is no canonical reference implementation of Data Mesh. Therefore, every organisation adopting Data Mesh has to plan to evolve their Data Platform and Operating Model over time. The best way to structure this evolution process is through many <a href="https://cloud.google.com/architecture/devops/devops-culture-transform">small iteration cycles</a> to experiment and learn the best way forward.</p><h3>4. Your organisational culture does not empower bottom-up decision-making</h3><p>When moving to a decentralised operating model, it is no longer feasible for any centralised body to maintain sufficient context or influence to make effective decisions in every distributed domain. Instead, you must trust in the distributed teams to autonomously find the best solution to the problems at hand.</p><p>Underpinning this mutual trust and individual autonomy is a culture of blamelessness and psychological safety to experiment, share knowledge, and learn together.</p><p>This <a href="https://cloud.google.com/architecture/devops/devops-culture-westrum-organizational-culture">article</a> describes how to implement, improve, and measure cultural capabilities that drive higher software delivery and organisational performance.</p><h3>5. You do not have clearly established roles &amp; responsibilities and incentive structure for distributed data teams</h3><p>Adopting Data Mesh requires navigating a number of new job roles such as Data Product Owner/Manager, Data Steward, Data Engineer, Data Scientist, or Analytics Engineer. Each plays a crucial function in enabling the distributed operating model.</p><p>These job roles and responsibilities must be standardised in order to create clarity of focus and to establish an incentivisation structure for these roles to work together to build the Data Mesh. Without this clarity and incentivisation structure, individuals may choose to prioritise other parts of their role over performing the necessary activities to build the Data Mesh such as building and sharing high-quality Data as Products.</p><h3>6. You do not have a critical mass of data talent</h3><p>To effectively make data and analytics a ubiquitous part of the business, every team will need to become more data-savvy. To achieve this, you may need to make a concerted effort to train your team members with skills such as data analysis, data visualisation, SQL, machine learning.</p><p>As adopting Data Mesh may require a fundamental shift in how a team operates, people who can champion new ways of working and help enable and empower distributed teams are critical to lead the organisation towards adopting these changes.</p><p>A distributed organisation with high individual autonomy cannot be successful without a critical mass of data talent and a structured approach for learning and enablement.</p><h3>7. Your data teams have low engineering maturity</h3><p><a href="https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance">High-performing engineering teams</a> deliver faster, more frequently, fail less often, and recover from failure more quickly. They adopt a number of <a href="https://cloud.google.com/architecture/devops/technical">best-practices</a> such as Continuous Integration and Continuous Delivery (CI/CD) to maintain high delivery velocity.</p><p>As automation is necessary for Data Mesh to deliver value at scale, high-performing engineering teams are more likely to apply these DevOps practices in their daily work.</p><p>Data teams relying on manual, ad-hoc, and one-off processes are unlikely to be able to develop reliable and trustworthy Data as Products. These properties of a Data Product are crucial to enable the Data Mesh to scale.</p><h3>8. You expect to find off-the-shelf software to help you adopt Data Mesh</h3><p>Like DevOps, Data Mesh is about more than just technology and tools. It is a mindset and cultural shift where teams adopt new ways of working.</p><p>Technology can only be the catalyst for cultural change. Furthermore, Data Mesh emphasises <em>how</em> technology can be used for data integration, rather than <em>what</em> technology to use. Therefore, it is unlikely that adopting any technology solution alone will help you realise value from Data Mesh.</p><h3>9. You do not have buy-in to “shift-left” security, privacy, and compliance</h3><p>Distributing ownership over data cannot result in lower security, privacy, and compliance standards. Instead, security, privacy, and compliance must become everyone’s responsibility.</p><p>Research from <a href="https://cloud.google.com/architecture/devops/devops-tech-shifting-left-on-security">DevOps Research and Assessment (DORA)</a> shows that teams can achieve better outcomes by making security a part of everyone’s daily work instead of testing for security concerns at the end of the process.</p><p>“Shifting-left” security, privacy, and compliance into development processes requires collaboration between relevant stakeholders and every embedded data team. Therefore, it is important to get buy-in from all relevant parties and involve security, privacy, and compliance stakeholders as early as possible when adopting Data Mesh.</p><h3>10. You do not consider Data Governance to be a core activity to be prioritised against other activities in every data team’s backlog</h3><p>Federated Computational Governance is a fundamental principle of Data Mesh, with an emphasis on automation and standardisation in order to enable more comprehensive and real-time monitoring, detection, and remediation of policy violations.</p><p>Like Security &amp; Privacy, Data Governance must “shift-left” to become a part of daily work for every data team. As such, Data Governance concerns such as enhancing Data and Metadata quality needs to be prioritised in every data team’s backlog. To embed Data Governance into standard development processes, these activities can be raised as tickets directly to the relevant data team’s backlog, or automated as tests that every code change must pass in order to be integrated and deployed to production.</p><p>To drive automation, standardisation, and best-practices, you may need to establish specialist engineering teams who can develop tooling/processes and provide specialist advisory to help distributed teams meet Data Governance policies and standards more easily.</p><h3>Conclusion</h3><p>Data Mesh is not a silver bullet for all your data management problems. It can be challenging — maybe even unrealistic — to implement for many organisations.</p><p>Regardless, I predict that many large organisations looking to scale impact from data and analytics will eventually adopt some version of Data Mesh; however not every element of Data Mesh will be implemented, or at least not immediately. For example, building a reusable and self-serviceable Data Platform as a Product is already emerging as a best-practice for cloud adoption. This requires implementing the platform using infrastructure-as-code and CI/CD with embedded and continuous controls, setting the foundations for Federated Computational Governance. Once organisations are confident that they can operate the Cloud Data Platform safely and at-scale, Decentralised Data Ownership can be adopted widely. This might in turn prompt adjustment over Data Domain boundaries and even the org chart to allow distributed data teams to effectively develop Data as Product.</p><p>Instead of trying to implement every element of Data Mesh, I would recommend first focusing on how you can empower your data teams to deliver value faster and more frequently for your customers, then work backwards to identify and adopt specific elements of Data Mesh that will help you to achieve this goal.</p><p>Hope you’ve found this article useful / interesting / thought-provoking. Please share and leave comments if you do.</p><p>Checkout a podcast I recently recorded with Scott Hirleman (founder of the Data Mesh Learning Community) where I went into more details on each point in this article: <a href="https://daappod.com/data-mesh-radio/are-you-ready-for-data-mesh-thinh-ha/">https://daappod.com/data-mesh-radio/are-you-ready-for-data-mesh-thinh-ha/</a></p><p><em>Special thanks to my colleagues Magdalena Algawam, Pradeep Bhattiprolu, Razvan Culea, Radek Stankiewicz, and Ada Tagoe for your help reviewing this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a0b045ea40f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/10-reasons-why-you-should-not-adopt-data-mesh-7a0b045ea40f">10 reasons why you are not ready to adopt data mesh</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>