<?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 Ashish Gupta on Medium]]></title>
        <description><![CDATA[Stories by Ashish Gupta on Medium]]></description>
        <link>https://medium.com/@ashishkumarg5?source=rss-000f6d45a995------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9gsSaW-0vXeVkddS</url>
            <title>Stories by Ashish Gupta on Medium</title>
            <link>https://medium.com/@ashishkumarg5?source=rss-000f6d45a995------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:33:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ashishkumarg5/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[What is a Data Mesh ?]]></title>
            <link>https://medium.com/@ashishkumarg5/what-is-a-data-mesh-1faa65e9a3f9?source=rss-000f6d45a995------2</link>
            <guid isPermaLink="false">https://medium.com/p/1faa65e9a3f9</guid>
            <category><![CDATA[data-mesh]]></category>
            <dc:creator><![CDATA[Ashish Gupta]]></dc:creator>
            <pubDate>Sat, 03 Aug 2024 17:16:58 GMT</pubDate>
            <atom:updated>2024-08-03T17:16:58.814Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a Data Mesh ?</h3><p>In a big organization, there can be multiple different teams responsible for different business area. In first generation data platform architectures, we majorly relied on Centralized data warehouses for storing structured data from various sources and the building ETL pipelines and BI reporting on the same. In second generation data platform architectures (still mostly used), Data Lakes came to the rescue which are Centralized repositories to store raw, unstructured and semi-structured data at scale. This Centralized approach works just perfectly for small organizations with simpler domains and smaller number of data sources and consumers, but it fails for large organizations.</p><p>Although removing silos by decentralizing data storage is considered to be the first step towards data maturity, there are some challenges of having a centralized data model:</p><ol><li>A centralized system can become a bottleneck, specially as data volume and processing demand grows.</li><li>Centralized data model can introduce latency due to the need for data to travel to and from a central location. Heavy reliance on a central sytem can slow down data processing.</li><li>Single point of failure.</li><li>Operational complexity.</li><li>Centralized models can complicate compliance with data governance and privacy regulations.</li><li>Resource Allocation: Fixed resource allocation can lead to inefficiencies, with resources being ether underutilized or overprovisioned.</li></ol><p>These limitations have led to the evolution of more distributed and decentralized data architecture — DATA MESH</p><p>The data mesh architecture describes a modern data stack that moves away from a monolithic data lake or data warehouse architecture to a distributed domain-specific architecture that enables autonomy of data ownership, provides agility with decentralized domain aware data management while providing the ability to centrally govern and monitor data across domains.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1faa65e9a3f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>