How Data Mesh is helping supercharge Glovo
summary
Glovo adopts a Data Mesh, partners with Thoughtworks, and builds a central self‑service platform while ring‑fencing an enablement team to avoid firefighting; the first customer behavior data product (a full app conversion funnel) ships after about 10–11 months and is available via streaming, query and Looker. Architecture shifts from monolithic pipelines to domain-owned data products with federated governance enforced by computational checks. Early result: multiple domains now publish reusable products and business teams argue less about numbers and more about decisions.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:15What is Glovo
- 6:50Why Data Mesh
- 8:50Problems Glovo faced
- 10:15What happens if we continue operating this way
- 11:35Thoughtworks partnership
- 13:35Why Glovo chose Data Mesh
- 15:20Data is not tables anymore
- 16:25Building data products
- 18:53Building the first data product
- 22:45Data Mesh is live
- 23:45Focus areas going forward
related talks
30mHow To Select Technology For Data Mesh
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy
48mBuilding a data mesh
30mData Mesh – Architecture And Insights From The Self-service Platform Boosting Financial Services
31mData Mesh In Practice – How To Set Up A Data Driven Organization
47mData Mesh - a hot air balloon?
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
51mData Mesh – Successful with People, Process, and Technology