Mario Meir-Huber
The Data Mesh as the end of the Datalake as we know it
#1about 4 minutes
Why large corporations struggle with managing their data
Large enterprises face significant data challenges due to distributed ownership, complex legacy systems, and pervasive data silos.
#2about 5 minutes
The historical evolution from data warehouses to data lakes
Centralized data warehouses proved too expensive and inflexible, leading to the rise of data lakes which introduced new problems with governance and complexity.
#3about 2 minutes
Understanding data mesh as a concept, not a technology
The data mesh is an organizational and cultural blueprint for data handling, not a specific software or platform you can install.
#4about 6 minutes
Addressing the core failures of traditional data approaches
Traditional data strategies often fail by focusing on ETL pipelines and monolithic platforms instead of solving actual business problems.
#5about 4 minutes
Building a distributed and domain-driven data architecture
Data mesh aligns data architecture with business domains using microservices principles, ensuring solutions are simple and tailored to specific needs.
#6about 3 minutes
Leveraging self-serve platforms to accelerate data work
Adopting a self-serve platform design using public cloud services allows teams to focus on solving data problems instead of managing infrastructure.
#7about 2 minutes
Shifting the mindset to treat data as a product
The data-as-a-product principle holds domain teams responsible for the quality, availability, and accessibility of their data for others to consume.
#8about 6 minutes
Defining the essential attributes of a data product
A data product must be discoverable, addressable via APIs, trustworthy, self-describing with metadata, interoperable, and secure.
#9about 1 minute
Data mesh as a solution for modern data challenges
While not a silver bullet, the data mesh framework provides a more effective approach for managing data in large, complex organizations.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
11:05 MIN
Understanding the data mesh as a concept, not a product
A Data Mesh needs Open Metadata
05:25 MIN
Solving centralization bottlenecks with Data Mesh
Modern Data Architectures need Software Engineering
00:51 MIN
The evolution from data warehouses to data lakes
Modern Data Architectures need Software Engineering
29:42 MIN
Deployment models and the vision for a data mesh
GraphQL Mesh – Why GraphQL between services is the worst idea and the best idea at the same time!
16:47 MIN
Using DataWorks as a unified IDE for big data
Alibaba Big Data and Machine Learning Technology
00:14 MIN
The challenges of a centralized data lake architecture
A Data Mesh needs Open Metadata
00:43 MIN
Meeting modern application and data platform demands
Tomorrow's cloud data platforms - fully managed database-as-a-service (DBaaS)
25:26 MIN
Modern data architectures and the reality of team size
Modern Data Architectures need Software Engineering
Featured Partners
Related Videos
29:25Modern Data Architectures need Software Engineering
Matthias Niehoff
38:36A Data Mesh needs Open Metadata
Ferd Scheepers
50:06Single Server, Global Reach: Running a Worldwide Marketplace on Bare Metal in a Cloud-Dominated World
Jens Happe
43:13It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design
Carola Lilienthal
45:58Data Fabric in Action - How to enhance a Stock Trading App with ML and Data Virtualization
Andreas Christian
42:16Making Data Warehouses fast. A developer's story.
Adnan Rahic
19:44Blueprints for Success: Steering a Global Data & AI Architecture
Dominik Schneider
46:24The Rise of Reactive Microservices
David Leitner
From learning to earning
Jobs that call for the skills explored in this talk.
Senior Data Architect - Data Lake & AWS 95% remote ID02259
mund consulting AG
Senior
ETL
Java
JIRA
Scala
Python
+7