#173 Zhamak's Corner 13 - Preventing Unnecessary Data Movement - In Spirit and in Reality

<p><a href="https://www.patreon.com/datameshradio" rel="noopener noreferrer" target="_blank">Data Mesh Radio Patreon</a> - get access to interviews well before they are released</p><p>Episode list and links to all available episode transcripts (most interviews from #32 on) <a href="https://docs.google.com/spreadsheets/d/1ZmCIinVgIm0xjIVFpL9jMtCiOlBQ7LbvLmtmb0FKcQc/edit?usp=sharing" rel="noopener noreferrer" target="_blank">here</a></p><p>Provided as a free resource by DataStax <a href="https://www.datastax.com/products/datastax-astra?utm_source=DataMeshRadio" rel="noopener noreferrer" target="_blank">AstraDB</a>; George Trujillo's contact info: email (<a href="mailto:george.trujillo@datastax.com" rel="noopener noreferrer" target="_blank">george.trujillo@datastax.com</a>) and <a href="https://www.linkedin.com/in/georgetrujillo/" rel="noopener noreferrer" target="_blank">LinkedIn</a></p><p>For more great content from Zhamak, check out her book on <a href="https://www.oreilly.com/library/view/data-mesh/9781492092384/" rel="noopener noreferrer" target="_blank">data mesh</a>, <a href="https://www.oreilly.com/library/view/software-architecture-the/9781492086888/" rel="noopener noreferrer" target="_blank">a book she collaborated on</a>, <a href="https://www.linkedin.com/in/zhamak-dehghani/" rel="noopener noreferrer" target="_blank">her LinkedIn</a>, and <a href="https://twitter.com/zhamakd" rel="noopener noreferrer" target="_blank">her Twitter</a>.</p><p>In this episode, Scott and Zhamak covered the misconception many have when she says "leave the data where it is" - it's about leaving the ownership with those who should have it, not leaving the data in the source system. If you only do source system, all you have is current state, so your data isn't even immutable or bi-temporal! They also discussed the need to be smarter about processing data - should it be at the source or should it be on query? There isn't a universal approach but we also shouldn't have to move the data around just to process it, bring the processin