If you're still designing your stack with a separate transactional layer, an analytical warehouse, and a real-time tier stitched together by pipelines — H1 2026 just made that architecture harder to justify. Every major platform shipped something this half that chips away at the need for that middle layer. This week's issue breaks down exactly what ➡️ Snowflake, ➡️ Databricks, ➡️ BigQuery, ➡️ Redshift, and ➡️ MS Fabric each did — and what the pattern means for the rest of the year. Video version of this weeks www.datapro.news below 👇

For a decade our job was to make capability flow: Get the data in, get the model serving, ship the pipeline. After Washington switched off Claude Fable 5 for half the world overnight, there's a second mandate now - make capability survivable. ➡️ Designing for the provider disappearing. ➡️ For the model silently getting worse with no error. ➡️ For the legal status of your output being genuinely unsettled. Multi-model routing and dependency governance just moved from "nice architecture" to core competency. The engineers who can answer "what happens to this pipeline when the model goes dark?" are going to be the ones writing the architecture decisions for everyone else. Check out the video edition below 👇

It is proving that the data means what the enterprise says it means. That is why the launch of IRiS Assistant last week caught my attention. For Azure and Microsoft Fabric teams working with Data Vault, this could be a game changing signal. Not because AI has arrived in modelling, but because the assistant is targeting the awkward phase zero work: ➡️ Source profiling, ➡️ Business-key discovery, ➡️ Relationship mapping and metadata capture. This week’s newsletter looks at what matters, what still needs proving, and why Fabric data engineers should be paying attention. Check out this week's video edition of www.datapro.news 👇 IRiS Assistant announcement: https://ignition-data.com/iris

97 issues in, I wanted to stop and look at where we are heading. Not the weekly news. Not the tool releases or the model benchmarks. The bigger picture: What has actually happened to us as data engineers over the last two years, and what does it mean for where our careers go from here? The profession has split into two groups. One group is more in demand than ever. The other is already feeling the automation squeeze - and oftentimes they're not aware of it yet. This week's newsletter is a full retrospective across all 97 previous editions. I've traced the three forces that reshaped the job (one economic, one regulatory, one physical), named what separated the engineers who thrived from those who struggled, and mapped what the next horizon actually looks like from here. Checkout datapro.news Video edition here 👇 What is your read on where the profession is heading?

Six months on from the CES 2026 Atlas debut, the real story is what happens to your data stack when intelligence moves off the server and into the physical world. This week's edition of www.datapro.news is a check-in on how robotics is directly reshaping Enterprise Data and AI Management. We cover: 🎡 The Physical AI Flywheel — why circular, real-time pipelines are replacing batch ETL for good ✅ Demonstration quality scoring — mutual information estimation as the new data quality frontier 🤖 Synthetic data pipelines becoming core infrastructure, not a research investment Edge-cloud MLOps — what Jetson Thor actually changes for your deployment architecture. At $5.71/hr all-in versus $28/hr for a warehouse worker, the economic case has already been made. The data infrastructure question is no longer theoretical. Which of these shifts is closest to landing in your organisation right now — pipeline architecture, data quality, or MLOps at the edge? This week's edition is in your inbox. 👇