How Integration & Api Creation & Life Cycles Are Critical To Your Data Mesh Strategy
summary
Argues that SnapLogic fills gaps in data mesh by putting an API manager at the heart of a federated data-as-a-service model, supporting ELT/ETL, application and real-time streaming patterns and hybrid infrastructure. Claims low-code/no-code design-time feedback reduces build-and-break cycles and developer need, speeding delivery; warns uncontrolled cross-team copying can create ~10x data growth. Describes a single platform for orchestration, connectors and governance that survives cloud platform swaps.
AI-written summary · about
chapters (15)
- 0:00Introduction and context
- 3:40Understanding data fabric
- 5:29Data mesh fundamentals
- 8:42Domain-driven design in data
- 10:26Data as a service concept
- 12:35Federation and integration challenges
- 14:02API management in data mesh
- 16:07SnapLogic’s integration platform
- 17:31Automation and federation journey
- 18:32AI and future of data platforms
- 20:46API manager in the architecture
- 21:48Platform independence benefits
- 22:57Speed and productivity gains
- 24:42Design-time data feedback
- 25:03Event and next steps
related talks
09mCuring modern data architecture complexity
21mSimplify Your Data Stack: Automate Orchestrate and Integrate Data
20mEmbracing Data Mesh: A Modern Strategy for Scalable Data Management
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy
39mData Mesh symphony: Orchestrating a synchronized data and business strategy ensemble
51mData Mesh – Successful with People, Process, and Technology
36mIntroducing Data Mesh A Paradigm Shift In Analytical Data Management Architecture
45mRethink Data Accessibility: Data Mesh meets Enterprise Integration