the audio is rather quiet, compared to other tracks on Soundcloud

Gogol Bordello - Bublitschki

Everybody Knows '88 by Leonard Cohen

Element Of Crime - bring den Vorschlaghammer mit

Patti Smith - A Hard Rain's A-Gonna Fall (live)(Dylan Nobel Ceremony December 2016)

Electro By Myself

Ständchen

Epitaph (King Crimson cover)

08 OperaBabes - Scheherazade

In this podcast, Daniel Bryant sat down with Zhamak Dehghani, principal consultant, member of technical advisory board, and portfolio director at ThoughtWorks. Topics discussed included: the motivations for becoming a data-driven organization; the challenges of adapting legacy data platforms and ETL jobs; and how to design and build the next generation of data platforms using ideas from domain-driven design and product thinking, and modern platform principles such as self-service workflows.

Why listen to this podcast:

 - Becoming a data-driven organization remains one of the top strategic goals of many organizations. Being able to rapidly run experiments and efficiently analyse the resulting data can provide a competitive advantage.
 - There are several “architecture failure modes” within existing enterprise data platforms. They are centralized and monolithic. The composition of data pipelines are often highly-coupled, meaning that a change to the data format will require a cascade of changes throughout the pipeline. And finally, the ownership of data platforms is often siloed and hyper-specialized.
 - The next generation of enterprise data platform architecture requires a paradigm shift towards ubiquitous data with a distributed data mesh.
Instead of flowing the data from domains into a centrally owned data lake or platform, domains need to host and serve their domain datasets in an easily consumable way.
 - Domain data teams must apply product thinking to the datasets that they provide; considering their data assets as their products, and the rest of the organization's data scientists, ML and data engineers as their customers.
The key to building the data infrastructure as a platform is (a) to not include any domain specific concepts or business logic, keeping it domain agnostic, and (b) make sure the platform hides all the underlying complexity and provides the data infrastructure components in a self-service manner.


More on this: Quick scan our curated show notes on InfoQ https://bit.ly/39exTWl
You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Check the landing page on InfoQ: https://bit.ly/39exTWl

InfoQ Podcast

Show Notes

Zhamak Dehghani on Data Mesh, Domain-Oriented Data, and Building Data Platforms

"things change" from no-man's 1994 album"flowermouth".

Tim Bowness - vocals. Ben Coleman - violin.  Steven Wilson - instruments.

Produced by Steven Wilson.

"You're leaving me behind you -
leaving me behind.
Things change."

things change

Part of the Radialnacht concert with the Mahler Chamber Orchestra @ Radialsystem,
May 3rd 2013

Arvo Pärt - Fratres (Remix)

Software engineers, architects and team leads have found inspiration to drive change and innovation in their team by listening to the weekly InfoQ Podcast. They have received essential information that helped them validate their software development map. We have achieved that by interviewing some of the top CTOs, engineers and technology directors from companies like Uber, Netflix and more. Over 1,200,000 downloads in the last 3 years.

Zhamak Dehghani on Data Mesh, Domain-Oriented Data, and Building Data Platforms

InfoQ

Recent comments

AudBitPart

Related tracks