How Data Mesh architecture and Data Catalogs help decentralized data teams.

-

Not too long ago, Data Administrators had to change their long habit of having a monolith database.

They were forced to accept and agree to the Polyglot persistence - the developer's teams have started to choose different data storage and technologies that would support each application team's data model requirements.

The time has arrived to break down also the Data Lake monolith paradigm. 

Refactoring monolith Data Lake makes a lot of sense.  

The central data lake as well as the central data team is often a huge bottleneck. The central data team is usually busy with fixing broken data pipes and taking care of constant data changes made by the domain owners/development teams. 

Data Mesh architecture is coming to the rescue here. Instead of a centralized data team, there would be multiple decentralised domain data teams, producing data sets or consuming other teams' data sets. Domain data team usually knows their domain data very well and are aware of any changes that are happening. 

Data Mesh architecture helps organizations to grow and scale data infrastructures fast without any inter-dependencies. 

One of the keys to organized data lake decentralization is clear Data Visibility through Data Catalog.

Interdependent domain teams, that consume each other's data,  as well as Data Analysts, Data Scientists need to have a clear understanding of each Data Mesh Data Asset characteristics:
  1. Data Metadata and Lineage, 
  2. Data Quality, 
  3. Data Freshness 
  4. Data Availability.

Data Catalog is an organized centralized data assets inventory in the organization that would discover Data Assets and their metadata across data domains.

Data Catalogs will answer questions, similar to "Where is this data living?", "Who is the data set owner?", "How often is this data set updated?", "Where is this data coming from?", "Which datasets is this dashboard taking data from?", "How the data is being used"

Data Catalogs would enable the domain teams and data analysts to find relevant data assets, enforce common business vocabulary, and ensure data freshness and correctness.

Which Data Catalog products are you using in your organization?






Comments

Post a Comment

Popular posts from this blog

Unlocking Microsoft Fabric: A Simple Guide when you only have a personal account.

-
Image
" You cannot create a Microsoft capacity using a personal account. Use your organizational account instead." What a disappointment and frustration! I've been trying to set up Microsoft Fabric for a while now and figure out how to work around this error. I use my personal Gmail for an MVP subscription to learn and experiment with Azure services. When I visit app.fabric.microsoft.com and try to use my private Gmail address, I keep getting a similar message: It's frustrating because I'm eager to dive into Fabric and explore its capabilities. I would get the same error trying to set up Azure Data Catalog, PowerBI embedded, and more. What are the different account types and how do they differ? A work or school account is created through Active Directory or other cloud directory services, such as Microsoft 365. On the other hand, a personal account is one that's manually created for individual use, consisting simply of a username and password. After digging into ...
Read more

ETL to ELT journey: Break free your Transformations and discover Happiness and Data Zen

-
Every data integration pipeline consists of 3 stages: Data Extraction (E), Data Transformation (T) and Data Load (L) During the  Data Extraction stage, the source data is read from its origins: transactional databases, CRM or ERP systems or through data scraping from web pages. During the  Data Transformation stage, the necessary modifications are applied to the source data. This includes data filtering, enrichment or merging with existing or other source datasets, data obfuscation, dataset structure alignment or validation, fields renaming and data structuring, according to the canonical data warehouse model.  During the Data Loading stage, the data is stored in the pipeline destination, which could be a staging area, data lake or data warehouse. There are two principal methods for the data integration process: transferring it from where it originated to the destination, where the data will be used for analysis, ETL and ELT. The difference between ETL and ELT pipelines...
Read more

Coding is a rollercoaster of efficiency and eyebrow-raising discoveries.

-
Image
Data Engineers or Developers - many of us love to be gourmet chefs in the kitchen. When it comes to planning and design, we would rather throw all ingredients in the pot and see how it comes out.  Coding without a plan is like assembling a puzzle in a dark room. The result will most probably be unexpected and off the canvas. Whether you follow Waterfall or Agile development strategy, planning and design phases are non-negotiable and are essential to reduce development cycles and redo work. Once upon a time, one data engineer created an amazing piece-of-cake automation pipeline. This masterpiece had very complex logic, pulling data from multiple sources, and merging and persisting the data in a complex, incremental way. When the pipeline started to run successfully and automation flows worked, the data engineer got very excited and considered this development done. A few days later QA engineer found out that the result dataset was never created in the destination. Why has that ...
Read more